In ARC review, the Sun GNOME team was asked to change the
SMF service name for GDM from application/gdm-login.xml to
application/graphical-login/gdm.
GDM is the non-default login program, recommended for use
by users who require accessibility, and ARC has also required
the following:
If a system has GDM enabled via SMF using the old name, that
the system should still start GDM on next reboot. I've been
thinking how to do this, and have come up with the following
ideas:
1) In post-install, run "svcs gdm-login" and see if it is
"online". If so, run "svcadm disable gdm-login" and
"svcadm enable gdm". I don't think this solution would
work, because if GDM is enabled, then restarting this
service would log the user out and terminate the install.
GDM probably wouldn't start up properly because the install
would have been stopped in the middle.
It doesn't seem that there are any svcadm options to
say "I want to keep the process running until reboot, but
on next reboot don't start this and instead start something
else".
2) Change the boot process so that this check is done sometime
before SMF tries to start GDM.
3) The install script/program could run these commands at the
end of the install, causing GDM to restart and kill any running
user sessions. The script/program could prompt the user to
click "OK" or something before restarting to allow them to
save data/close windows, etc.
Note this would only be necessary for users who are using GDM
as their login program and wouldn't be needed for users who
have CDE login or console login enabled.
4) Tell the user to manually run the svcadm commands on next
reboot.
I'm sure that this is the sort of thing that projects will have
to manage, so I'm guessing there is a recommended way to do this.
Ideas?
Thanks,
Brian
