01-29-2019
Quote:
Originally Posted by
DOkuwa
I am trying to fire up a GUI in my Unix server as root
Usually you cannot do that. An "X-Server" runs on the
client, not the server. You might want to read my
little introduction about X-Windows for a clcarification on how X-Windows works.#
I hope this helps.
bakunin
This User Gave Thanks to bakunin For This Post:
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
What types of error messages would I recieve if the backbone of the network is setup for both Unix and Windows systems? (6 Replies)
Discussion started by: Aisha Sturkey
6 Replies
2. Windows & DOS: Issues & Discussions
I recently got myself a new 2 TB drive.
However everytime I connect the drive it doesn't have a drive letter, so I have to open the diskmgmt.msc and manually reassign it (EVERY TIME I connect the Drive...)
Also the Drive appears to have no Recycle Bin.
It always prompts to instantly delete... (4 Replies)
Discussion started by: pasc
4 Replies
3. Windows & DOS: Issues & Discussions
Hi,
I have a desktop it's about seven to eight years old. It has Windows XP. When I open I.E or Firefox or Google Chrome, I get so many other popup.
I did install CClearner and spybot search & Destroy. But still I am getting lot of popup. crazy picture of girls comes on the screen.
... (8 Replies)
Discussion started by: samnyc
8 Replies
4. Shell Programming and Scripting
Greetings Experts,
I need to pass a parameter to ksh and the value is windows path eg: sh abc.txt C:\Users\chill3chee\Desktop
No matter I try with \ delimiter, still could not get this exact value assigned to the shell variable which was checked with echo. Tried with using... (2 Replies)
Discussion started by: chill3chee
2 Replies
5. Red Hat
Hello Friends,
I have observed one recent issue about ftp from windows to Linux.
Initially we had Solaris unix and any file sent from windows to solaris via ftp (binary or ascii) worked smoothly.
Say for e.g if I sent a shell script to soalris from windows, that script used to run corectly.... (17 Replies)
Discussion started by: Albert_Pinto7
17 Replies
6. Windows & DOS: Issues & Discussions
I had a simple automation process to take config backup from san switches to windows via SSH. This can be accomplished using plink.
My script was working fine earlier but from last few days it is not collecting data and the error which i am getting is below.
"":confused:
I have done the... (6 Replies)
Discussion started by: nirjhar17
6 Replies
7. UNIX for Beginners Questions & Answers
Hi there,
I am trying to understanding the difference between X11, host- based versus user-based access controls. And how vulnerability can the X11 settings be and why it is recommended to turn it off. (1 Reply)
Discussion started by: alvinoo
1 Replies
LEARN ABOUT OSF1
xdestroywindow
XDestroyWindow(3X11) XDestroyWindow(3X11)
NAME
XDestroyWindow, XDestroySubwindows - destroy windows
SYNOPSIS
XDestroyWindow(display, w)
Display *display;
Window w;
XDestroySubwindows(display, w)
Display *display;
Window w;
ARGUMENTS
Specifies the connection to the X server. Specifies the window.
DESCRIPTION
The XDestroyWindow function destroys the specified window as well as all of its subwindows and causes the X server to generate a DestroyNo-
tify event for each window. The window should never be referenced again. If the window specified by the w argument is mapped, it is
unmapped automatically. The ordering of the DestroyNotify events is such that for any given window being destroyed, DestroyNotify is gener-
ated on any inferiors of the window before being generated on the window itself. The ordering among siblings and across subhierarchies is
not otherwise constrained. If the window you specified is a root window, no windows are destroyed. Destroying a mapped window will generate
Expose events on other windows that were obscured by the window being destroyed.
XDestroyWindow can generate a BadWindow error.
The XDestroySubwindows function destroys all inferior windows of the specified window, in bottom-to-top stacking order. It causes the X
server to generate a DestroyNotify event for each window. If any mapped subwindows were actually destroyed, XDestroySubwindows causes the X
server to generate Expose events on the specified window. This is much more efficient than deleting many windows one at a time because much
of the work need be performed only once for all of the windows, rather than for each window. The subwindows should never be referenced
again.
XDestroySubwindows can generate a BadWindow error.
DIAGNOSTICS
A value for a Window argument does not name a defined Window.
SEE ALSO
XChangeWindowAttributes(3X11), XConfigureWindow(3X11), XCreateWindow(3X11), XMapWindow(3X11), XRaiseWindow(3X11), XUnmapWindow(3X11)
Xlib -- C Language X Interface
XDestroyWindow(3X11)