Alan:
Thanks for your comments. Really appreciated.
> gdm(1m):
>
>> The Automatic Login feature which will cause GDM to bypass
>> the login greeter GUI entirely and immediately start a ses-
>> sion for the user specified in the GDM configuration.
>
> The "which" seems to be out of place there.
Good catch. I removed the word "which" from the above sentence.
>> XDMCP
>> By default, XDMCP is disabled in GDM.
>
> It would probably be good at the start of the XDMCP section to explain
> what XDMCP is for those not familiar with the acronym - just a sentence
> or two such as:
>
> XDMCP displays the login screen and resulting session
> on a remote machine over the network interface. By
> default, XDMCP is disabled in GDM....
I added the above text to the beginning of the XDMCP section, though
I also spell out the acronym also as follows:
XDMCP (X Display Manager Control Protocol) displays the
login screen and resulting session on a remote machine over
the network interface. By default, XDMCP is disabled in
> The gdm man page should probably have an added section about SMF, giving
> it's service name and references to svcadm, like most of the other services
> controlled by SMF on Solaris - see the "SMF PROPERTIES" section in dtlogin(1)
> or the SMF references in hald(1m) for instance.
>
> gdm-stop(1m):
>
>> gdm-stop stops the GDM daemon process by sending a TERM sig-
>> nal to the GDM daemon. This command immediately terminates
>> all sessions and logs out users currently logged in with
>> GDM.
>
> But won't smf immediately restart it? Should this just tell you to do
> svcadm disable gdm instead? (unless you manually started gdm and didn't
> svcadm enable it)
I added the following paragraph to the end of the DESCRIPTION.
On Solaris, the GDM service is managed by the smf(5) service
management facility under the service identifier
svc:/application/graphical-login/gdm. On Solaris, it is
recommended that you use the svcadm(1m) utility to start and
stop the GDM service instead of using gdm-stop(1m).
I also made a similar change to the gdm(1m) manpage where it makes
mention of gdm-stop:
If you wish to stop the GDM service, you can either send a
TERM signal to the main GDM daemon, or run the gdm-stop(1m)
command. On Solaris, the GDM service is managed by the
smf(5) service management facility under the service iden-
tifier svc:/application/graphical-login/gdm. On Solaris, it
is recommended that you use the svcadm(1m) utility to start
and stop the GDM service instead of using gdm-stop(1m).
Previously the manpage only had the first sentence of the above
paragraph.
> gdmdynamic(1m):
>
> -l pattern List displays that are started via the
> gdmdynamic command.
> Without a pattern, all attached displays
> are lsited.
>
> Typo: s/lsited/listed/
Fixed, thanks.
> BTW, at this years X.Org Developers Conference we got a demo of a
> dynamic multiseat system using USB hotpluggable devices that provide
> a DisplayLink video output port and USB keyboard/mouse/audio [1] and they
> talked about how gdmdynamic made it all possible [2]. We of course pointed
> out that Sun contributed to that for Sun Rays 8-)
>
> [1] http://plugable.com/
> [2] http://libdlo.freedesktop.org/wiki/MultiSeatTerminal
Cool.
Brian
