The XDM or console login X session is not the only sort. The X session is really on the Xserver, which in general might not even be local. Any sort of X process can attach to it regardless of the existence of a login. For instance, without a login, you could:
Maybe your question is more about the login process. One X app can spawn another and then terminate. The X Server defines which X using client process is part of which "X Session", which is every X client attached to that display. If the display server is not taken down between logins, then X clients of the prior login could persist on it. For the console, the text on the screen and that shell need a new home on the face of the X display, and generally that process is critical to the X Server, being the parent, so if you kill that window, you lose the whole x window desktop, and when X clients lose their connection to the X Server, they tend to exit.
Hello,
I have created a web page on a server using apache and added .htaccess and .htpasswd in the folder for authentification.
I was wondering if there was anyway to tie-in the login for this page with the login used to logon to the server.
i.e. the same login info. is used for both,... (2 Replies)
Hello,
I have created a web page on a server using apache and added .htaccess and .htpasswd in the folder for authentification.
I was wondering if there was anyway to tie-in the login for this page with the login used to logon to the server.
i.e. the same login info. is used for both, when... (1 Reply)
I am unable to launch Xsession from my windows desktop to Sun Solairs 10 OS, its giving xdmcp error. Please guide me what changes I need to do in Solaris.
Thanks (1 Reply)
I am trying to set up my Xsession to run on an AIX server calling it from the command line when I telnet to it. I can access the X-window using exceed but not from issueing the Xsession command from a simple telnet or SSH session. Is it possible to have AIX open the Xwindow when called from a... (0 Replies)
Hello World ~
HW : SUN Fire V240
OS : Solaris 8
Error message prompts 'rmclomv ... SC login failure ...' on terminal.
and
Error Message prompts continually 'SC Login Failure for user Please login:' on Single Mode(init S)
The System is in normal operation, though
In case of rain, Can... (1 Reply)
I am attempting to run Xsession as a non root user and it fails. If I start exceed log into the server as roots via putty ssh with X11 forwarding on I can startX run xclock, but when I su - user and export DISPLAY=client IP:0 then attempt to startx, xclock it hangs for a minute and I receive the... (1 Reply)
Can someone please tell me how to run xsession startup scripts whenever I start or after I restart my X session? I'm not trying to do anything fancy I just want this to run. This makes life a lot easier when I use a dual monitor.
xrandr --output VGA1 --mode 1024x768 --rate 60 (7 Replies)
Hey folks,
When a user is added to a new group, the user has to be log out and log in again to make the new group effective. Is there any system command or technique to refresh user group ID update without re-login?
I am not talking about to use "login" or "su -l" commands which can only make... (2 Replies)
Discussion started by: hce
2 Replies
LEARN ABOUT X11R4
startx
STARTX(1) General Commands Manual STARTX(1)NAME
startx - initialize an X session
SYNOPSIS
startx [ [ client ] options ... ] [ -- [ server ] [ display ] options ... ]
DESCRIPTION
The startx script is a front end to xinit that provides a somewhat nicer user interface for running a single session of the X Window Sys-
tem. It is often run with no arguments.
Arguments immediately following the startx command are used to start a client in the same manner as xinit(1). The special argument '--'
marks the end of client arguments and the beginning of server options. It may be convenient to specify server options with startx to
change on a per-session basis the default color depth, the server's notion of the number of dots-per-inch the display device presents, or
take advantage of a different server layout, as permitted by the Xorg(1) server and specified in the xorg.conf(5) file. Some examples of
specifying server arguments follow; consult the manual page for your X server to determine which arguments are legal.
startx -- -depth 16
startx -- -dpi 100
startx -- -layout Multihead
To determine the client to run, startx first looks for a file called .xinitrc in the user's home directory. If that is not found, it uses
the file xinitrc in the xinit library directory.
If command line client options are given, they override this behavior and revert to the xinit(1) behavior. To determine the server to run,
startx first looks for a file called .xserverrc in the user's home directory. If that is not found, it uses the file xserverrc in the
xinit library directory. If command line server options are given, they override this behavior and revert to the xinit(1) behavior. Users
rarely need to provide a .xserverrc file. See the xinit(1) manual page for more details on the arguments.
The system-wide xinitrc and xserverrc files are found in the /usr/local/lib/X11/xinit directory.
The .xinitrc is typically a shell script which starts many clients according to the user's preference. When this shell script exits,
startx kills the server and performs any other session shutdown needed. Most of the clients started by .xinitrc should be run in the back-
ground. The last client should run in the foreground; when it exits, the session will exit. People often choose a session manager, window
manager, or xterm as the ''magic'' client.
EXAMPLE
Below is a sample .xinitrc that starts several applications and leaves the window manager running as the ''last'' application. Assuming
that the window manager has been configured properly, the user then chooses the ''Exit'' menu item to shut down X.
xrdb -load $HOME/.Xresources
xsetroot -solid gray &
xbiff -geometry -430+5 &
oclock -geometry 75x75-0-0 &
xload -geometry -80-0 &
xterm -geometry +0+60 -ls &
xterm -geometry +0-100 &
xconsole -geometry -0+0 -fn 5x7 &
exec twm
ENVIRONMENT VARIABLES
DISPLAY This variable gets set to the name of the display to which clients should connect. Note that this gets set, not
read.
XAUTHORITY This variable, if not already defined, gets set to $(HOME)/.Xauthority. This is to prevent the X server, if not
given the -auth argument, from automatically setting up insecure host-based authentication for the local host.
See the Xserver(1) and Xsecurity(7) manual pages for more information on X client/server authentication.
FILES
$(HOME)/.xinitrc Client to run. Typically a shell script which runs many programs in the background.
$(HOME)/.xserverrc Server to run. The default is X.
/usr/local/lib/X11/xinit/xinitrc
Client to run if the user has no .xinitrc file.
/usr/local/lib/X11/xinit/xserverrc
Server to run if the user has no .xserverrc file.
SEE ALSO xinit(1), Xserver(1), Xorg(1)X Version 11 xinit 1.1.1 STARTX(1)