


User Commands                                   gdm-screenshot(1)



NAME
     gdm-screenshot - GDM Screenshot Application

SYNOPSIS
     gdm-screenshot [--debug] [--help]

DESCRIPTION
     gdm-screenshot is a utility for generating a  PNG  image  of
     the  currently running GDM login GUI screen.  It is normally
     launched by pressing the key defined as the screenshot  key-
     binding.   The  resulting  image  is  saved  to a file named
     /var/run/gdm/GDM-Screenshot.png.

OPTIONS
     The following options are supported:

     -d, --debug     Display debug output.



     -h, --help      Display detailed usage message.



EXAMPLES
     Example 1: Take a screenshot.

     example% gdm-screenshot

FILES
     The following files are used by this application:

     /usr/bin/gdm-screenshot

         Executable for GDM Dynamic Server Management.



     /var/run/gdm/GDM-Screenshot.png

         Resulting image file created when gdm-screenshot is run.



ATTRIBUTES
     See attributes(5) for descriptions of the  following  attri-
     butes:








SunOS 5.11          Last change: 22 Oct 2009                    1






User Commands                                   gdm-screenshot(1)



     ____________________________________________________________
    |       ATTRIBUTE TYPE        |       ATTRIBUTE VALUE       |
    |______________________________|______________________________|
    | Availability                | SUNWgnome-display-mgr       |
    |______________________________|______________________________|
    | Interface stability         | Volatile                    |
    |______________________________|______________________________|


SEE ALSO
     Latest version of the _G_N_O_M_E  _D_e_s_k_t_o_p  _U_s_e_r  _G_u_i_d_e  for  your
     platform.

     gdmdynamic(1),  gdmflexiserver(1),  gdm(1m),   gdm-stop(1m),
     attributes(5)

NOTES
     Written by  Brian  Cameron,  Sun  Microsystems  Inc.,  2009.
     Copyright (c) 2009 by Sun Microsystems, Inc.




































SunOS 5.11          Last change: 22 Oct 2009                    2






Maintenance Commands                                 gdm-stop(1m)



NAME
     gdm-stop - Stop the GDM daemon process

SYNOPSIS
     gdm-stop

DESCRIPTION
     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.

     On Solaris, the GDM service is managed by the smf(5) service
     management    facility    under   the   service   identifier
     _s_v_c:/_a_p_p_l_i_c_a_t_i_o_n/_g_r_a_p_h_i_c_a_l-_l_o_g_i_n/_g_d_m.   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).

FILES
     The following files are used by this application:

     /usr/bin/gdm-stop               Executable for Stop the  GDM
                                     daemon process.



ATTRIBUTES
     See attributes(5) for descriptions of the  following  attri-
     butes:

     ____________________________________________________________
    |       ATTRIBUTE TYPE        |       ATTRIBUTE VALUE       |
    |______________________________|______________________________|
    | Availability                | SUNWgnome-display-mgr       |
    |______________________________|______________________________|
    | Interface stability         | Volatile                    |
    |______________________________|______________________________|


SEE ALSO
     Latest version of the _G_N_O_M_E  _D_e_s_k_t_o_p  _U_s_e_r  _G_u_i_d_e  for  your
     platform.

     gdmdynamic(1),     gdmflexiserver(1),     gdm-screenshot(1),
     gdm(1m), svcadm(1m), attributes(5), smf(5)

NOTES
     Written by Brian Cameron, Sun Microsystems Inc., 2004, 2006,
     2009.






SunOS 5.11          Last change: 20 Oct 2009                    1






Maintenance Commands                                      gdm(1m)



NAME
     gdm, gdm-binary - GDM (GNOME Display Manager)

SYNOPSIS
     gdm | gdm-binary [--debug] [--fatal-warnings]  [--help]  [--
     timed-exit] [--version]

DESCRIPTION
     GDM is the GNOME Display Manager, a program used  for  login
     session  management.   GDM  supports  managing  the  console
     display, other attached displays, XDMCP displays, and flexi-
     ble  (or on-demand) displays.  Flexible displays make use of
     the Virtual Terminals (VT) interfaces to allow user  switch-
     ing,  so  that  multiple users can run simultaneous sessions
     sharing the same console.  GDM  uses  ConsoleKit  to  manage
     what  sessions  are  active  on  the system.  GDM supports a
     number of configuration interfaces which  are  described  in
     later sections of this manpage.

     The gdm-binary program is the actual program  which  manages
     the  displays  on  the system, while gdm is a wrapper script
     that launches the gdm-binary program and  passes  along  any
     options.   Before  launching  gdm-binary,  the  gdm  wrapper
     script sources the system profile(4) file  to  set  standard
     system   environment   variables,  and  sets  the  LANG  and
     LC_MESSAGES environment variables to support internationali-
     zation.

     For each display that GDM is configured to manage, the  gdm-
     binary  program  will  launch  a slave daemon which does the
     work to actually manage the display.  The slave daemon  will
     start  the  login  greeter GUI program, the program that the
     user interacts with.  Refer the the "Login Greeter GUI" sec-
     tion below for more information about how the user interface
     works.

     If Virtual Terminals are supported on your system,  you  can
     start  a  flexible  display  via  the  "User Switcher" panel
     applet.  You may need to add this applet to  your  panel  to
     make use of it.  You can also use the gdmflexiserver(1) com-
     mand to start flexible displays from the command line.

     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 _s_v_c:/_a_p_p_l_i_c_a_t_i_o_n/_g_r_a_p_h_i_c_a_l-_l_o_g_i_n/_g_d_m.  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).

     GDM supports libaudit and Solaris auditing.   Refer  to  the
     bsmconv(1m) manpage for more information about how to enable



SunOS 5.11          Last change: 24 Oct 2009                    1






Maintenance Commands                                      gdm(1m)



     Solaris auditing.  On Solaris, GDM uses  logindevperm(4)  to
     ensure that device permissions are set properly for the user
     on login.

OPTIONS
     The following options are supported by gdm and gdm-binary:

     --debug                 Enable debug output.



     --fatal-warnings        Make all warnings fatal.  Useful for
                             debugging.



     --timed-exit            Exit after 30 seconds.   Useful  for
                             debugging.



     --version               Display the GDM version.



ENVIRONMENT VARIABLES
     See environ(5) for descriptions of environment variables.

     When the following description refers  to  "scripts",  these
     are  referring  to  the GDM Init, PostLogin, PreSession, and
     PostSession scripts.

     DESKTOP_SESSION

         For any user session started by  GDM,  this  environment
         variable  is set to the session name the user has chosen
         in the login GUI, such as "gnome" to indicate  that  the
         /usr/share/xsession/gnome.desktop  session file was used
         to launch the session.



     DISPLAY

         When running scripts and for any user session started by
         GDM,  this  environment  variable  is set to the Xserver
         display value associated with the session.



     DESKTOP_SESSION




SunOS 5.11          Last change: 24 Oct 2009                    2






Maintenance Commands                                      gdm(1m)



         For any user session started by  GDM,  this  environment
         variable is set to the keyboard layout that the user has
         chosen in the login GUI.



     HOME

         When running scripts and for any user session started by
         GDM, this environment variable is set to the home direc-
         tory associated with the user.



     LANG

         For any user session started by  GDM,  this  environment
         variable is set to the langauge choice selected when the
         user logged in.



     REMOTE_HOST

         When running scripts, this environment variable  is  set
         to  the  hostname  if  the  session  is  non-local (e.g.
         XDMCP).



     RUNNING_UNDER_GDM

         When running scripts, this environment variable  is  set
         to  "true", so that they can identify when they are exe-
         cuted by the GDM process.



     SHELL

         When running scripts and for any user session started by
         GDM, this environment variable is set to the shell asso-
         ciated with the session.



     USER

         When running scripts and for any user session started by
         GDM,  this  environment  variable is set to the username
         associated with the session.




SunOS 5.11          Last change: 24 Oct 2009                    3






Maintenance Commands                                      gdm(1m)



     USERNAME

         When running scripts and for any user session started by
         GDM,  this  environment  variable is set to the username
         associated with the session.



     XAUTHORITY

         When running scripts and for any user session started by
         GDM,  this  environment  variable  is set to the Xserver
         Xauthority file being used by the session.



     XDG_SESSION_COOKIE

         This environment variable is provided by ConsoleKit, and
         this value is set for any user session started by GDM so
         that ConsoleKit can properly identify the session.



EXTENDED DESCRIPTION
  Login Greeter GUI
     The login greeter GUI allows the user to specify  how  their
     user  session  should  be  started and ensures that the user
     authenticates before gaining access to their  user  session.
     Authentication can be disabled if desired.

     GDM makes use of pam(3PAM) to manage how the user  authenti-
     cates (for example, by entering a username and password, via
     a SmartCard, fingerprint reader, etc.).   If  authentication
     is  not desired, then GDM provides two configuration options
     which can be used to bypass it: "Automatic Login" and "Timed
     Login".  These are not enabled by default, but can be turned
     on if desired.

     The Automatic Login feature will cause  GDM  to  bypass  the
     login  greeter  GUI entirely and immediately start a session
     for the user specified in the GDM configuration.  The  Timed
     Login  feature  will  display  the  login  greeter GUI for a
     number of seconds specified in the GDM configuration.  If no
     user logs in before the timeout, then GDM will automatically
     start the user session for the user  specified  in  the  GDM
     configuration.   Timed  Login  is useful if you wish to have
     the opportunity to login as a different user on  some  occa-
     sions.  Obviously neither Automatic Login or Timed Login are
     secure, and they should only be used on  systems  where  the
     security provided by authentication is not needed.




SunOS 5.11          Last change: 24 Oct 2009                    4






Maintenance Commands                                      gdm(1m)



     GDM normally uses a PAM stack named "gdm".   When  Automatic
     Login or Timed Login is enabled, then GDM instead uses a PAM
     stack named "gdm-autologin".  Note that Automatic Login  and
     Timed  Login  will  not work properly if the "gdm-autologin"
     PAM stack is not defined in your PAM configuration.

     The login greeter GUI provides two mechanisms for specifying
     which  user  is  logging  into the system.  Either the "Face
     Browser" can be used, or GDM can prompt the  user  with  the
     requests  specified  by  the  system  PAM configuration.  By
     default, this means entering both the username and  password
     by hand.

     The Face Browser is designed to work when PAM is  configured
     to allow users to select their username, so it is not useful
     with certain PAM configurations (such as when  the  username
     is  identified  via  a  SmartCard or fingerprint).  The Face
     Browser obviously exposes usernames to anyone with access to
     the machine, so users may wish to disable it if this is con-
     sidered a security issue.

     When the Face Browser is  enabled,  a  list  of  users  will
     appear  in  the login greeter GUI.  An icon for each user is
     shown, and users can specify what icon  is  associated  with
     their  user.   If  the user has an image file named ~/.face,
     then GDM will associate this image with the  user.   If  the
     user  does  not  have  such an image file, a default icon is
     displayed.  Image files must be no larger than 64K in  size,
     or they are ignored by GDM.

     The login greeter GUI can be configured  to  provide  "Shut-
     down",  "Reboot", and "Suspend" buttons which allow the user
     to shutdown, reboot, or suspend the system if desired.

     While the login greeter GUI is displayed, a  panel  is  pro-
     vided  at  the  bottom  of  the screen which provides useful
     information, interfaces that allow the user to  specify  how
     their  session should be started, and interfaces to help the
     user navigate the login screen.  These include:

       +o  A clock, showing the date and time.

       +o  What type of session to run.

       +o  An alternative language to use.

       +o  An alternative keyboard layout (if supported).

       +o  The ability to launch assistive technology programs  if
          desired.

       +o



SunOS 5.11          Last change: 24 Oct 2009                    5






Maintenance Commands                                      gdm(1m)



          The ability to monitor the system battery (if  using  a
          system with a battery).


     The login greeter  GUI  also  allows  the  user  to  take  a
     screenshot.   If  the  user presses the keybindng associated
     with printing the screen, then the gdm-screenshot is run  to
     take the screenshot.

  Accessibility
     GDM supports accessibility.  Users can click on the accessi-
     bility icon on the panel to specify which assistive programs
     should be launched with the login GUI programs.  It is  also
     possible to configure a system so that needed assistive pro-
     grams should always be launched.

  Security
     The GDM login GUI programs are run with a dedicated user  id
     and group id.  By default "gdm" is used for both the user id
     and group id, but these values are configurable.  The reason
     for  using  this special user and group is to make sure that
     the GDM user interfaces run as a  user  without  unnecessary
     privileges,  so that in the unlikely case that someone finds
     a weakness in the GUI,  they  will  not  gain  access  to  a
     privileged account on the machine.

     Note that the GDM user and group  do  have  some  privileges
     beyond  what  a  normal  user  has.  This user and group has
     access to the Xserver authorization directory which contains
     all  of  the  Xserver  authorization files and other private
     information.  This means that  someone  who  gains  the  GDM
     user/group  privileges  can  then  connect  to  any  running
     Xserver session.  Do not, under any circumstances, make  the
     GDM user/group a user/group that might be easy to get access
     to, such as the user "nobody".

     File permissions are set on the authorization files so  that
     only the user has read and write access to ensure that users
     are unable to access the authorization  files  belonging  to
     other users.

  XDMCP
     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
     GDM.  However, GDM can be configured to enable XDMCP so that
     users can  log  into  the  system  from  remote  hosts.   By
     default,  GDM  listens to UDP port 177, although this can be
     configured.   GDM  responds  to  QUERY  and  BROADCAST_QUERY
     requests by sending a WILLING packet to the originator.





SunOS 5.11          Last change: 24 Oct 2009                    6






Maintenance Commands                                      gdm(1m)



     GDM provides configuration options that make GDM more resis-
     tant to denial-of-service attacks on the XDMCP service.  The
     default values should work for  most  systems,  but  several
     protocol  parameters, handshaking timeouts, and so on can be
     fine-tuned to make it more secure.  It  is  not  recommended
     that you modify the XDMCP configuration unless you know what
     you are doing.

     GDM grants access to the hosts specified in the GDM  service
     section  of  your TCP Wrappers configuration file.  Refer to
     the libwrap(3) manpage for more information.  GDM  does  not
     support remote display access control on systems without TCP
     Wrapper support.

     GDM can also be configured to  honor  INDIRECT  queries  and
     present  a host chooser to the remote display. GDM remembers
     the user's choice and forwards subsequent  requests  to  the
     chosen manager. GDM also supports an extension to the proto-
     col which makes GDM forget the redirection once  the  user's
     connection  succeeds.   This  extension is only supported if
     both daemons are GDM.  This extension is transparent and  is
     ignored by XDM or other daemons that implement XDMCP.

     GDM only supports the MIT-MAGIC-COOKIE-1 authentication sys-
     tem.  Because  of this, the cookies are transmitted as clear
     text. Therefore, you should be  careful  about  the  network
     where  you  use  this.  That is, be careful about where your
     XDMCP connection is going. Note that if snooping  is  possi-
     ble, an attacker could snoop your password as you log in, so
     a better XDMCP authentication would not help you  much  any-
     way. If snooping is possible and undesirable, you should use
     ssh(1) for tunneling an  X  connection,  rather  then  using
     GDM's  XDMCP.  Think of XDMCP as a sort of graphical telnet,
     with the same security issues.

  GDM Configuration
     ConsoleKit interfaces are used to configure how  GDM  should
     manage  displays in a multiseat environment, so to configure
     multiseat please refer to  the  console-kit-daemon(1m)  man-
     page.

     GDM also provides a number of configuration interfaces which
     allow  the user to specify how GDM should operate.  The con-
     figuration available for the GDM daemon and  the  GDM  login
     greeter  GUI are described below.  GDM also provides script-
     ing interfaces and other interfaces to  configure  how  ses-
     sions  are  started  which  are  described in the "GDM Login
     Scripts and Session Files" section of this manpage.

     The default system  configuration  for  the  GDM  daemon  is
     stored in the file /etc/gdm/gdm.schemas, and accessed by GDM
     via GConf.  Users are not recommended to  modify  this  file



SunOS 5.11          Last change: 24 Oct 2009                    7






Maintenance Commands                                      gdm(1m)



     since  it  may  be  overwritten  on  upgrade.  Instead users
     should override these settings by specifying values  in  the
     /etc/gdm/custom.conf file, which is in standard INI format.

     The settings below are in "group/key=_d_e_f_a_u_l_t__v_a_l_u_e"  format,
     so  to  override  the "xdmcp/Enable" value, you would modify
     the /etc/gdm/custom.conf so it contains these lines:

     [xdmcp]
     Enable=true

     The following keys are supported  for  configuring  the  GDM
     daemon:

     chooser/Multicast=false

         If true and IPv6 is enabled, the  chooser  will  send  a
         multicast   query  to  the  local  network  and  collect
         responses from  the  hosts  who  have  joined  multicast
         group.



     chooser/MulticastAddr=ff02::1

         This is the Link-local Multicast address.



     daemon/Group=gdm

         The group id used to run the login GUI programs



     daemon/TimedLoginEnable=false

         If the user given in  TimedLogin  should  be  logged  in
         after  a number of seconds (set with TimedLoginDelay) of
         inactivity on the login screen. This is useful for  pub-
         lic  access  terminals  or perhaps even home use. If the
         user uses the keyboard or browses the menus, the timeout
         will  be  reset to TimedLoginDelay or 30 seconds, which-
         ever is higher. If the user does not  enter  a  username
         but  just  hits the ENTER key while the login program is
         requesting the username, then GDM will assume  the  user
         wants  to login immediately as the timed user. Note that
         no password will be asked for this user so you should be
         careful,  although  if using PAM it can be configured to
         require password entry before allowing login.





SunOS 5.11          Last change: 24 Oct 2009                    8






Maintenance Commands                                      gdm(1m)



     daemon/TimedLogin=

         This is the user that should be logged in after a speci-
         fied number of seconds of inactivity.  If the value ends
         with a vertical bar | (the pipe symbol), then  GDM  will
         execute  the program specified and use whatever value is
         returned on standard out from the program as  the  user.
         The program is run with the DISPLAY environment variable
         set so that it is possible to  specify  the  user  in  a
         per-display   fashion.  For  example  if  the  value  is
         "/usr/bin/getloginuser|",     then      the      program
         /usr/bin/getloginuser will be run to get the user value.



     daemon/TimedLoginDelay=30

         Delay in seconds before the  TimedLogin   user  will  be
         logged in.



     daemon/AutomaticLoginEnable=false

         If true, the user given  in  AutomaticLogin   should  be
         logged in immediately.  This feature is like timed login
         with a delay of 0 seconds.



     daemon/AutomaticLogin=

         This is the user that should be logged in immediately if
         AutomaticLoginEnable  is true.  If the value ends with a
         vertical bar | (the pipe symbol), then GDM will  execute
         the program specified and use whatever value is returned
         on standard out from the program as the user.  The  pro-
         gram is run with the DISPLAY environment variable set so
         that it is possible to specify the user in a per-display
         fashion.     For     example    if    the    value    is
         "/usr/bin/getloginuser|",     then      the      program
         /usr/bin/getloginuser will be run to get the user value.



     daemon/User=gdm

         The username under which the greeter and other GUI  pro-
         grams are run.






SunOS 5.11          Last change: 24 Oct 2009                    9






Maintenance Commands                                      gdm(1m)



     security/DisallowTCP=false

         If true, then always append -nolisten tcp  to  the  com-
         mand  line  when starting attached Xservers, thus disal-
         lowing TCP connection. This is a more secure  configura-
         tion if you are not using remote connections.



     xdmcp/DisplaysPerHost=1

         To prevent attackers from filling up the pending  queue,
         GDM  will only allow one connection for each remote com-
         puter. If you want to provide display services  to  com-
         puters  with  more  than one screen, you should increase
         this value.  Note that the number of  attached  DISPLAYS
         allowed  is  not  limited.  Only  remote connections via
         XDMCP are limited by this configuration option.



     xdmcp/Enable=false

         Setting this to  true  enables  XDMCP  support  allowing
         remote  displays/X  terminals  to be managed by GDM.  If
         GDM is  compiled  to  support  it,  access  from  remote
         displays  can  be  controlled  using  the  TCP  Wrappers
         library.



     xdmcp/HonorIndirect=true

         Enables XDMCP INDIRECT choosing (i.e.  remote  execution
         of gdmchooser) for X-terminals which do not supply their
         own display browser.



     xdmcp/MaxPending=4

         To avoid denial of service attacks, GDM has  fixed  size
         queue  of  pending connections. Only MaxPending displays
         can start at the  same  time.   Please  note  that  this
         parameter  does  not limit the number of remote displays
         which can be managed.  It  only  limits  the  number  of
         displays initiating a connection simultaneously.



     xdmcp/MaxSessions=16




SunOS 5.11          Last change: 24 Oct 2009                   10






Maintenance Commands                                      gdm(1m)



         Determines the maximum number of remote display  connec-
         tions  which  will  be  managed simultaneously. I.e. the
         total number of remote displays that can use your host.



     xdmcp/MaxWait=30

         When GDM is ready to manage a display an  ACCEPT  packet
         is  sent to it containing a unique session id which will
         be used in future XDMCP conversations.   GDM  will  then
         place  the  session  id in the pending queue waiting for
         the display to respond with a  MANAGE  request.   If  no
         response  is  received  within MaxWait seconds, GDM will
         declare the display dead and erase it from  the  pending
         queue freeing up the slot for other displays.



     xdmcp/MaxWaitIndirect=30

         The MaxWaitIndirect  parameter  determines  the  maximum
         number  of seconds between the time where a user chooses
         a host and the subsequent indirect query where the  user
         is  connected to the host. When the timeout is exceeded,
         the information about the chosen host is  forgotten  and
         the  indirect  slot  freed  up  for  other displays. The
         information may be forgotten earlier if there  are  more
         hosts trying to send indirect queries then MaxPendingIn-
         direct.



     xdmcp/PingIntervalSeconds=15

         Interval in which to ping the Xserver in seconds. If the
         Xserver  does  not  respond before the next time we ping
         it, the connection is stopped  and  the  session  ended.
         This  is  a  combination  of  the  XDM  PingInterval and
         PingTimeout, but in seconds.



     xdmcp/Port=177

         The UDP port number  gdm  should  listen  to  for  XDMCP
         requests.



     xdmcp/Willing=/etc/gdm/Willing




SunOS 5.11          Last change: 24 Oct 2009                   11






Maintenance Commands                                      gdm(1m)



         When the machine sends a WILLING  packet  back  after  a
         QUERY it sends a string that gives the current status of
         this server. The default message is the system  ID,  but
         it  is possible to create a script that displays custom-
         ized message.  If this script does not exist or this key
         is  empty  the  default message is sent.  If this script
         succeeds and produces some output,  the  first  line  of
         it's  output  is sent (and only the first line). It runs
         at most once every 3 seconds to prevent possible  denial
         of service by flooding the machine with QUERY packets.



     The default system configuration for the GDM  login  greeter
     GUI  is  stored in the system GConf schemas directory in the
     file gdm-simple-greeter.schemas, and  accessed  by  GDM  via
     GConf.   Users  are not recommended to modify this file file
     since it may  be  overwritten  on  upgrade.   Instead  users
     should override these settings by modifying the GConf confi-
     guration for  the  GDM  user  (the  user  specified  in  the
     Daemon/User  configuration  key  above),  normally the "gdm"
     user.  Users can use the gconftool-2(1)  or  gconf-editor(1)
     programs to set these values, if desired.

     The following keys are supported  for  configuring  the  GDM
     login  greeter  GUI  and  are  in  "GConf  key=_d_e_f_a_u_l_t__v_a_l_u_e
     (_g_c_o_n_f__d_a_t_a__t_y_p_e)" format:

     /apps/gdm/simple-greeter/banner_message_enable=false
     (boolean)

         Controls whether the banner message text is displayed.



     /apps/gdm/simple-greeter/banner_message_text=NULL (string)

         Specifies the text banner message to show on the greeter
         window.



     /apps/gdm/simple-greeter/debug=false (boolean)

         If true, then debugging mode is enabled for the greeter.



     /apps/gdm/simple-greeter/disable_restart_buttons=false
     (boolean)

         Controls whether to show  the  restart  buttons  in  the



SunOS 5.11          Last change: 24 Oct 2009                   12






Maintenance Commands                                      gdm(1m)



         login window.



     /apps/gdm/simple-greeter/disable_user_list=true (boolean)

         If true, then the face browser with known users  is  not
         shown in the login window.



     /apps/gdm/simple-greeter/logo_icon_name=computer (string)

         Set to the themed icon name to use for the greeter logo.



     /apps/gdm/simple-greeter/wm_use_compiz=false (boolean)

         Controls whether compiz is used as  the  window  manager
         instead of metacity.



     /desktop/gnome/interface/accessibility=false (boolean)

         Controls whether the Accessibility  infrastructure  will
         be  started  with  the  GDM GUI. This is needed for many
         accessibility technology programs to work.



     /desktop/gnome/applications/at/screen_magnifier_enabled=false
     (boolean)

         If set, then the assistive tools linked  to  this  GConf
         key will be started with the GDM GUI program. By default
         this is a screen magnifier application.



     /desktop/gnome/applications/at/screen_keyboard_enabled=false
     (boolean)

         If set, then the assistive tools linked  to  this  GConf
         key will be started with the GDM GUI program. By default
         this is an on-screen keyboard application.



     /desktop/gnome/applications/at/screen_reader_enabled=false
     (boolean)



SunOS 5.11          Last change: 24 Oct 2009                   13






Maintenance Commands                                      gdm(1m)



         If set, then the assistive tools linked  to  this  GConf
         key will be started with the GDM GUI program. By default
         this is a screen reader application.



     On Solaris, GDM also supports the  CONSOLE,  PASSREQ,  PATH,
     and  SUPATH  configuration  options  in  /etc/default/login.
     Refer to the login(1) manpage for details.

  Logging
     GDM logs error and debug information to  the  system  syslog
     file.

     Output from the Xservers started by GDM is stored in the GDM
     log  directory,  /var/log/gdm.   The Xserver output for each
     display is saved in a file _d_i_s_p_l_a_y.log, where _d_i_s_p_l_a_y is the
     DISPLAY value for the associated display.

     Output from the GDM login greeter GUI is  saved  in  a  file
     _d_i_s_p_l_a_y-greeter.log  and output from the GDM slave daemon is
     saved in a file _d_i_s_p_l_a_y-slave.log.  Again,  the  _d_i_s_p_l_a_y  is
     the DISPLAY value for the associated display.

     Four older versions of each file are also stored, by append-
     ing 1 through 4 to the filename. These files are rotated, as
     new sessions on that display are started.

     The output  from  the  user  session  is  saved  in  a  file
     ~/.xsession-errors.   The  user session output is redirected
     before the PreSession script is started.

     Note that if the session is a failsafe session,  or  if  GDM
     cannot  open  this  file for some reason, a fallback file is
     created named /tmp/xses-_u_s_e_r.XXXXXX, where XXXXXX are random
     characters.

     If you run a system with  quotas  set,  consider  using  the
     PostSession script to delete the ~/.xsession-errors file, so
     that this log file is not stored unnecessarily.

EXIT STATUS
     The following exit values are returned:

     0        Application exited successfully



     >0       Application exited with failure






SunOS 5.11          Last change: 24 Oct 2009                   14






Maintenance Commands                                      gdm(1m)



FILES
     The following files are used by this application:

     /usr/sbin/gdm

         Wrapper script that launches GNOME Display Manager



     /usr/sbin/gdm-binary

         Executable for GNOME Display Manager.



  GDM Login Scripts and Session Files
     The following GDM login integration interfaces are discussed
     below:

       +o  /etc/gdm/Init/Default
       +o  /etc/gdm/Init/_d_i_s_p_l_a_y
       +o  /etc/gdm/PostLogin/Default
       +o  /etc/gdm/PostLogin/_d_i_s_p_l_a_y
       +o  /etc/gdm/PreSession/Default
       +o  /etc/gdm/PreSession/_d_i_s_p_l_a_y
       +o  /etc/gdm/Xsession
       +o  /etc/X11/xinit/xinitrc.d
       +o  /etc/profile
       +o  ~/profile
       +o  /etc/X11/xinit/xinitrc.d
       +o  /etc/gdm/PostSession/Default
       +o  /etc/gdm/PostSession/_d_i_s_p_l_a_y

     The following session files are also discussed below:

       +o  /usr/share/gdm/autostart/LoginWindow/*.desktop
       +o  /usr/share/xsessions/*.desktop
       +o  ~/.dmrc(default user session)

     The Init, PostLogin, PreSession, and PostSession scripts all
     work as described below.

     For each type of script, the default one which will be  exe-
     cuted is called "Default" and is stored in a directory asso-
     ciated with the script type. So the default Init  script  is
     /etc/gdm/Init/Default.   A  per-display  script  can be pro-
     vided, and if it exists  it  will  be  run  instead  of  the
     default  script.  Such scripts are stored in the same direc-
     tory as the default script and have the  same  name  as  the
     Xserver  DISPLAY value for that display. For example, if the
     /etc/gdm/Init/:0  script exists, it will be run for  DISPLAY
     ":0".



SunOS 5.11          Last change: 24 Oct 2009                   15






Maintenance Commands                                      gdm(1m)



     All of these scripts are run with root privilege and  return
     0  if  run successfully, and a non-zero return code if there
     was any failure that should cause the login  session  to  be
     aborted.  Also  note  that  GDM will block until the scripts
     finish, so if any of these scripts hang, this will cause the
     login process to also hang.

     When the Xserver for the login  GUI  has  been  successfully
     started, but before the login GUI is actually displayed, GDM
     will run the Init script. This script is useful for starting
     programs  that should be run while the login screen is show-
     ing, or for doing any special initialization if required.

     After the user has been successfully authenticated GDM  will
     run  the  PostLogin  script. This is done before any session
     setup    has    been    done,    including    before     the
     pam_open_session(3PAM) call. This script is useful for doing
     any session initialization that needs to happen  before  the
     session  starts.  For  example,  you  might setup the user's
     $HOME directory if needed.

     After the user session has been initialized,  GDM  will  run
     the  PreSession  script. This script is useful for doing any
     session initialization that needs to happen after  the  ses-
     sion  has  been  initialized.  It  can  be  used for session
     management or accounting, for example.

     When a user terminates their session, GDM will run the Post-
     Session script. Note that the Xserver will have been stopped
     by the time  this  script  is  run,  so  it  should  not  be
     accessed.

     Note that the PostSession script will be run even  when  the
     display  fails  to  respond  due to an I/O error or similar.
     Thus, there is no guarantee that X  applications  will  work
     during script execution.

     All of the above  scripts  will  set  the  RUNNING_UNDER_GDM
     environment  variable  to  "yes".  If  the  scripts are also
     shared with other display managers, this allows you to iden-
     tify  when  GDM  is  calling  these  scripts, so you can run
     specific code when GDM is used.

     The /usr/share/gdm/autostart/LoginWindow directory  contains
     .desktop  files.   Any .desktop files in this directory will
     cause the associated program to automatically start with the
     login  GUI  greeter.  By  default, GDM is shipped with files
     which  will  autostart  the  gdm-simple-greeter  login   GUI
     greeter  itself,  the  gnome-power-manager  application, the
     gnome-settings-daemon,  and  the  metacity  window  manager.
     These  programs  are needed for the greeter program to work.
     In addition, desktop files are provided for starting various



SunOS 5.11          Last change: 24 Oct 2009                   16






Maintenance Commands                                      gdm(1m)



     AT  programs  if  the associated accessibility configuration
     GConf keys are set.

     The user's default session and language choices  are  stored
     in the ~/.dmrc file. When a user logs in for the first time,
     this file is created with the user's  initial  choices.  The
     user can change these default values by simply changing to a
     different value when logging  in.  GDM  will  remember  this
     change for subsequent logins.

     The session types which  are  available  in  the  GDM  login
     greeter  GUI are specified by .desktop files.  These desktop
     files are in standard INI format  and  the  executable  that
     will  be run to start the session is specified by the "Exec"
     key in the file.  Desktop files are normally stored  in  the
     /usr/share/xsessions  directory.   However,  GDM will search
     for desktop files  in  the  following  directories  in  this
     order:         /etc/X11/sessions/,         /etc/dm/Sessions,
     /usr/share/xsessions, and /usr/share/gdm/BuiltInSessions.

     The /etc/gdm/Xsession script is called between  the  PreSes-
     sion  and the PostSession scripts. This script does not sup-
     port per-display like the other scripts. This script is used
     for  actually  starting the user session. This script is run
     as the user, and it will run whatever session was  specified
     by the Desktop session file the user selected to start.  The
     /etc/gdm/Xsession script will source  /etc/profile,  ~/.pro-
     file, and all scripts in the /etc/X11/xinit/xinitrc.d direc-
     tory before starting the user session.  Refer  to  the  pro-
     file(4) manpage for more information.

  Configuration Files
     /etc/gdm/gdm.schemas

         GDM default daemon configuration.



     /etc/gdm/custom.conf

         GDM daemon configuration customization.



     /etc/gconf/schemas/gdm-simple-greeter.schemas

         GDM default login greeter GUI configuration.



     /etc/default/login




SunOS 5.11          Last change: 24 Oct 2009                   17






Maintenance Commands                                      gdm(1m)



         On Solaris, GDM supports the CONSOLE, PASSREQ, PATH, and
         SUPATH  configuration  options.   Refer  to the login(1)
         manpage for details.



     ~gdm/.gconf.mandatory

         The GDM user's mandatory GConf settings.



     ~gdm/.gconf

         The GDM user's GConf settings.



     ~gdm/.gconf.path

         This file specifies the GDM user's mandatory GConf  set-
         tings directory.



  Logging
     /var/log/gdm/_d_i_s_p_l_a_y.log

         Xserver output for each _d_i_s_p_l_a_y.



     /var/log/gdm/_d_i_s_p_l_a_y-greeter.log

         GDM login greeter GUI output for each _d_i_s_p_l_a_y.



     /var/log/gdm/_d_i_s_p_l_a_y-slave.log

         GDM slave daemon output for each _d_i_s_p_l_a_y.



     ~/.xsession-errors

         Output from the user session.



  GDM Xauthority files




SunOS 5.11          Last change: 24 Oct 2009                   18






Maintenance Commands                                      gdm(1m)



     /var/run/gdm

         Stores the Xserver authentication files for each managed
         session.



  Face Browser
     /usr/share/pixmaps/faces

         Global directory for face images.



     ~/.face

         User-defined icon to be used by GDM face browser.



  GDM user cache
     /var/cache/gdm

         GDM copies the  user's  ~/.dmrc  and  ~/.face  files  to
         /var/cache/gdm/_u_s_e_r_n_a_m_e, so that they can be accessed on
         subsequent logins without  accessing  the  user's  $HOME
         directory before pam_setcred(3PAM) is called.



ATTRIBUTES
     See attributes(5) for descriptions of the  following  attri-
     butes:

     ____________________________________________________________
    |       ATTRIBUTE TYPE        |       ATTRIBUTE VALUE       |
    |______________________________|______________________________|
    | Availability                | SUNWgnome-display-mgr       |
    |______________________________|______________________________|
    | Interface stability         | Volatile                    |
    |______________________________|______________________________|
    | /etc/X11/gdm/custom.conf    | Volatile                    |
    |______________________________|______________________________|
    | ~gdm/.gconf.mandatory       | Volatile                    |
    |______________________________|______________________________|
    | ~gdm/.gconf                 | Volatile                    |
    |______________________________|______________________________|


SEE ALSO
     More information can be found at:




SunOS 5.11          Last change: 24 Oct 2009                   19






Maintenance Commands                                      gdm(1m)



     http://library.gnome.org/admin/gdm

     Latest version of the _G_N_O_M_E  _D_e_s_k_t_o_p  _U_s_e_r  _G_u_i_d_e  for  your
     platform.

     gdmdynamic(1),     gdmflexiserver(1),     gdm-screenshot(1),
     gconftool-2(1),     gconf-editor(1),    login(1),    ssh(1),
     Xserver(1),   console-kit-daemon(1m),   bsmconv(1m),    gdm-
     stop(1m),    svcadm(1m),   libwrap(3),   pam(3PAM),   login-
     devperm(4),    pam.conf(4),    profile(4),    attributes(5),
     environ(5), smf(5)

NOTES
     This man page written by Martin K.  Petersen  <mkp@mkp.net>,
     George    Lebl    <jirka@5z.com>,    and    Brian    Cameron
     <brian.cameron@sun.com>.  Copyright (c) 1998, 1999 by Martin
     K. Petersen.  Copyright (c) 2001, 2003, 2004 by George Lebl.
     Copyright (c) 2003 by Red Hat,  Inc.   Copyright  (c)  2006,
     2009 by Sun Microsystems, Inc.




































SunOS 5.11          Last change: 24 Oct 2009                   20






User Commands                                   gdmflexiserver(1)



NAME
     gdmflexiserver - Runs flexible (on demand) X servers

SYNOPSIS
     gdmflexiserver  [--authenticate]   [--command=_c_o_m_m_a_n_d]   [--
     debug] [--monte-carlo-pi] [--no-lock] [--version] [--xnest]

DESCRIPTION
     gdmflexiserver is primarily used to run flexible (on demand)
     X  servers  via  the  virtual  terminal interface.  gdmflex-
     iserver allows a user to log in once and then  quits.   This
     is  useful  if you are logged in as user A, and user B wants
     to log in quickly but user A does not wish to log out.   The
     X  server  ensures that the virtual terminal switching works
     transparently.

     In GDM 2.20 and  earlier,  gdmflexiserver  was  the  primary
     interface  for  starting flexible X server sessions.  In the
     current version of GDM, the "User Switcher" panel applet  is
     more  typically  used  for this purpose when using the GNOME
     desktop.  The gdmflexiserver interface is provided for back-
     wards  compatibility  purposes,  and to provide an interface
     for starting flexible X server sessions when not  using  the
     GNOME desktop.

     Many of the gdmflexiserver options are no  longer  supported
     in  GDM  and are ignored if used.  For example, GDM 2.20 and
     earlier made use of the --command option to  query  informa-
     tion  from  the  GDM  daemon  and  to  control its behavior.
     Current versions of GDM  use  D-Bus  for  this  purpose  and
     gdmflexiserver now only supports the "VERSION" command.

OPTIONS
     The following options are supported:

     -a, --authenticate              Ignored.



     -c, --command=_c_o_m_m_a_n_d           Run the specified command.



     -d, --debug                     Enable debugging output.



     --monte-carlo-pi                Easter egg.   Determine  the
                                     value  of  pi  using a Monte
                                     Carlo simulation.





SunOS 5.11          Last change: 20 Oct 2009                    1






User Commands                                   gdmflexiserver(1)



     -l, --no-lock                   Ignored.



     --version                       Display GDM version number.



     -n, --xnest                     Ignored.



EXTENDED DESCRIPTION
     gdmflexiserver accepts  the  following  with  the  --command
     option:

       +o  VERSION

     Each is described in detail in the following section:

  VERSION
     Description:            Query GDM version



     Supported since:        2.2.4.0



     Arguments:              None



     Answers:                GDM _g_d_m-_v_e_r_s_i_o_n



EXAMPLES
     Example 1: To see the GDM version

     example% gdmflexiserver --command=VERSION
     GDM  2.28.1

FILES
     The following files are used by this application:

     /usr/bin/gdmflexiserver         Executable for Run  flexible
                                     (on demand) X servers.







SunOS 5.11          Last change: 20 Oct 2009                    2






User Commands                                   gdmflexiserver(1)



ATTRIBUTES
     See attributes(5) for descriptions of the  following  attri-
     butes:

     ____________________________________________________________
    |       ATTRIBUTE TYPE        |       ATTRIBUTE VALUE       |
    |______________________________|______________________________|
    | Availability                | SUNWgnome-display-mgr       |
    |______________________________|______________________________|
    | Interface stability         | Volatile                    |
    |______________________________|______________________________|


SEE ALSO
     Latest version of the _G_N_O_M_E  _D_e_s_k_t_o_p  _U_s_e_r  _G_u_i_d_e  for  your
     platform.

     gdmdynamic(1),  gdm-screenshot(1),  gdm(1m),   gdm-stop(1m),
     attributes(5)

NOTES
     Original  man   page   written   by   Martin   K.   Petersen
     <mkp@mkp.net>,  George  Lebl  <jirka@5z.com>.  Copyright (c)
     1998, 1999 by Martin  K.   Petersen.   Copyright  (c)  2001,
     2003,  2004  by  George Lebl. Copyright (c) 2003 by Red Hat,
     Inc.

     Updated by Brian Cameron, Sun Microsystems Inc., 2004, 2006,
     2009.


























SunOS 5.11          Last change: 20 Oct 2009                    3



