From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020808 Description of problem: after adding another X server to gdm.conf and sending SIGHUP, the existing session is thrown out. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 0. be logged on to :0 1. add 1=Standard vt8 to [servers] in gdm.conf 2. kill -HUP `cat /var/run/gdm.pid` 3. wait a few seconds Actual Results: the X server on :0 was terminated Expected Results: the default /etc/X11/gdm/gdm.conf says: # (HUP will make gdm not kill existing sessions and will only restart gdm # after all users log out) Additional info: gdm-2.4.0.7-1
Potentially just bogus docs, I'm not sure.
Yeah, bogus doc. Should be USR1. HUP does immediate restart USR1 does safe restart. There are also two scripts gdm-restart and gdm-safe-restart that do this for you.
okay, thanks for the info. (I'd prefer HUP to be the safe restart, since that's what xdm does, but...) gdm-*restart isn't included in the RPM, but that's OK. one of these days I'm sure Red Hat will make the ${pref}dm run from a normal initscript, so we can write "service gdm reload" and have it do the right thing. a manual page would be nice, btw :-)
Can't do 'service gdm'. Other VTs aren't initialized yet, so X startup gets screwed.
Bogus docs fixed, nothing else to do besides educate users :)