Gordon: > How hard would it be to implement separate SMF service instances for gdm > so one could independently start or stop either of these: (say) > svc:/application/graphical-login/gdm:console > svc:/application/graphical-login/gdm:remote > > Where the first would control the console Xserver (of course) > and the second would control remote access via XDMCP. > > It's inconvenient having your login session killed when > using one of the above and restarting the other.
You can turn on/off Remote XDMCP support already, but not using SMF. Simply modify the GDM /usr/share/gdm/defaults.conf configuration file. Change the value for the "Enable" key in the "[xdmcp]" section to true or false. Then run this command to update GDM to recognize the new value: gdmflexiserver --command="UPDATE_CONFIG xdmcp/Enable" If it returns "OK", then it worked. It shouldn't fail. GDM should immediately start honoring the new configuration option without needing to restart. Likewise you can modify most GDM configuration values on the fly like this. Note if you have a value for the same key in your GDM custom.conf file, changes to the defaults.conf file will be ignored. So if it doesn't work, this is probably the issue. If that can be scripted into a SMF service instances, then we could do that. However, GDM doesn't provide any mechanism for starting/stopping the console display. To provide this feature, the upstream GDM codebase would need to be enhanced. Note that the GDM codebase is being rewritten, so any features added to the GDM 2.20 version we currently ship would likely need to also be implemented in the new codebase. Brian
