diff options
| author | George Lebl <jirka@5z.com> | 2003-07-19 23:35:37 +0000 |
|---|---|---|
| committer | George Lebl <jirka@src.gnome.org> | 2003-07-19 23:35:37 +0000 |
| commit | 19e695b94366fa5918c11a2fdf7281abd5239062 (patch) | |
| tree | 7a090e86af33b0e00559705aec454bcfadf8ccad | |
| parent | dec056b7317e7f43bebd287a3ca837076f0ab470 (diff) | |
| download | gdm-19e695b94366fa5918c11a2fdf7281abd5239062.tar.gz | |
update the documentation a lot and install the docs. Yay! We have actual
Sat Jul 19 16:33:19 2003 George Lebl <jirka@5z.com>
* docs/C/gdm.xml, configure.in, docs/C/Makefile.am,
docs/Makefile.am, xmldocs.make, omf.make: update the
documentation a lot and install the docs. Yay! We
have actual documentation now!!!
* daemon/misc.c: add sys/time.h and sys/resource.h includes
(from looking at the FreeBSD patches)
* daemon/slave.c: pass LOGIN_SETENV as well to setusercontext
(from looking at the FreeBSD patches)
* gui/gdmsetup.c: fix gccism, and look for the chown/chmod command
(from looking at the FreeBSD patches)
* gui/gdmphotosetup.c: add signal.h include
(from looking at the FreeBSD patches)
* configure.in, utils/Makefile.am: When the security/pam_misc.h is
available also test for where the misc_conv function is as it seems
to be sometimes compiled into the main libpam (FreeBSD for example)
(from looking at the FreeBSD patches)
* config/Default.in, config/Xsession.in, config/(Pre|Post)Session.in,
config/XKeepsCrashing: don't use command -v and use which properly.
And avoid stderr from which
* utils/gdmaskpass.c: use GETTEXT_PACKAGE here
* configure.in, utils/gdmtranslate.c, utils/Makefile.am,
config/XKeepsCrashing, config/Xsession.in, config/Makefile.am:
Add gdmtranslate libexec proggie since gettext command is not
always installed apparently (non-developer machines) so we
can't rely on it existing. Also do translations from the
Xsession script
* gui/gdmlogin.c, gui/greeter/greeter_system.c: Fix #117504 by
changing the tooltip to be more informative
* gui/greeter/greeter_system.c: Fix warnings when not all
system dialog possibilities are present
* Makefile.am, greeter.c, greeter.dtd, greeter_configuration.h,
greeter_item.[ch], greeter_item_customlist.[ch],
greeter_parser.[ch], greeter_system.c: Add listitem (proposed
as customitem to the release-team) tags that can be inside
a list and thus create custom widgetry. At this point all
custom widgetry that can be done is a list to pick from but
this should be possible to extend for some future releases.
This custom info is then written to a per display file
to use from login scripts or elsewhere. While I was there
I fixed leaks and crashes when the parser would find parse
errors.
* docs/C/gdmconfig/*, docs/C/gdm.sgml, docs/C/gdm-manual.txt:
remove everything here as it was old and unused and outdated.
61 files changed, 2474 insertions, 5689 deletions
@@ -1,3 +1,61 @@ +Sat Jul 19 16:33:19 2003 George Lebl <jirka@5z.com> + + * docs/C/gdm.xml, configure.in, docs/C/Makefile.am, + docs/Makefile.am, xmldocs.make, omf.make: update the + documentation a lot and install the docs. Yay! We + have actual documentation now!!! + + * daemon/misc.c: add sys/time.h and sys/resource.h includes + (from looking at the FreeBSD patches) + + * daemon/slave.c: pass LOGIN_SETENV as well to setusercontext + (from looking at the FreeBSD patches) + + * gui/gdmsetup.c: fix gccism, and look for the chown/chmod command + (from looking at the FreeBSD patches) + + * gui/gdmphotosetup.c: add signal.h include + (from looking at the FreeBSD patches) + + * configure.in, utils/Makefile.am: When the security/pam_misc.h is + available also test for where the misc_conv function is as it seems + to be sometimes compiled into the main libpam (FreeBSD for example) + (from looking at the FreeBSD patches) + + * config/Default.in, config/Xsession.in, config/(Pre|Post)Session.in, + config/XKeepsCrashing: don't use command -v and use which properly. + And avoid stderr from which + + * utils/gdmaskpass.c: use GETTEXT_PACKAGE here + + * configure.in, utils/gdmtranslate.c, utils/Makefile.am, + config/XKeepsCrashing, config/Xsession.in, config/Makefile.am: + Add gdmtranslate libexec proggie since gettext command is not + always installed apparently (non-developer machines) so we + can't rely on it existing. Also do translations from the + Xsession script + + * gui/gdmlogin.c, gui/greeter/greeter_system.c: Fix #117504 by + changing the tooltip to be more informative + + * gui/greeter/greeter_system.c: Fix warnings when not all + system dialog possibilities are present + + * Makefile.am, greeter.c, greeter.dtd, greeter_configuration.h, + greeter_item.[ch], greeter_item_customlist.[ch], + greeter_parser.[ch], greeter_system.c: Add listitem (proposed + as customitem to the release-team) tags that can be inside + a list and thus create custom widgetry. At this point all + custom widgetry that can be done is a list to pick from but + this should be possible to extend for some future releases. + This custom info is then written to a per display file + to use from login scripts or elsewhere. While I was there + I fixed leaks and crashes when the parser would find parse + errors. + + * docs/C/gdmconfig/*, docs/C/gdm.sgml, docs/C/gdm-manual.txt: + remove everything here as it was old and unused and outdated. + 2003-07-19 Christian Neumair <chris@gnome-de.org> * gui/gdmchooser-strings.c, gui/gdmsetup-strings.c: Use english diff --git a/Makefile.am b/Makefile.am index c4a80c7f..0e823eed 100644 --- a/Makefile.am +++ b/Makefile.am @@ -24,7 +24,9 @@ EXTRA_DIST = \ gdm-stop.in \ gdm-restart.in \ gdm-safe-restart.in \ - gdmconfig + gdmconfig \ + xmldocs.make \ + omf.make sbin_SCRIPTS = gdm-stop gdm-restart gdm-safe-restart gdmconfig diff --git a/config/Default.in b/config/Default.in index fec2e819..9cafb95e 100644 --- a/config/Default.in +++ b/config/Default.in @@ -7,22 +7,24 @@ PATH=@X_PATH@:$PATH sysmodmap=/etc/X11/Xmodmap -if command -v xmodmap > /dev/null 2>&1; then - if [ -z "$GDM_PARENT_DISPLAY" ]; then +XMODMAP=`which xmodmap 2>/dev/null` +if [ x$XMODMAP != x ] ; then + if [ x$GDM_PARENT_DISPLAY = x ]; then if [ -f $sysmodmap ]; then - xmodmap $sysmodmap + $XMODMAP $sysmodmap fi else - ( DISPLAY=$GDM_PARENT_DISPLAY XAUTHORITY=$GDM_PARENT_XAUTHORITY xmodmap -pke ) | xmodmap - + ( DISPLAY=$GDM_PARENT_DISPLAY XAUTHORITY=$GDM_PARENT_XAUTHORITY $XMODMAP -pke ) | $XMODMAP - fi fi -if command -v setxkbmap > /dev/null 2>&1; then +SETXKBMAP=`which setxkbmap 2>/dev/null` +if [ x$SETXKBMAP != x ] ; then # FIXME: is this all right? Is this completely on crack? # What this does is move the xkb configuration from the GDM_PARENT_DISPLAY # FIXME: This should be done in code. Or there must be an easier way ... if [ -n "$GDM_PARENT_DISPLAY" ]; then - XKBSETUP=`( DISPLAY=$GDM_PARENT_DISPLAY XAUTHORITY=$GDM_PARENT_XAUTHORITY setxkbmap -v )` + XKBSETUP=`( DISPLAY=$GDM_PARENT_DISPLAY XAUTHORITY=$GDM_PARENT_XAUTHORITY $SETXKBMAP -v )` if [ -n "$XKBSETUP" ]; then XKBKEYMAP=`echo "$XKBSETUP" | grep '^keymap' | awk '{ print $2 }'` XKBTYPES=`echo "$XKBSETUP" | grep '^types' | awk '{ print $2 }'` @@ -30,13 +32,13 @@ if command -v setxkbmap > /dev/null 2>&1; then XKBSYMBOLS=`echo "$XKBSETUP" | grep '^symbols' | awk '{ print $2 }'` XKBGEOMETRY=`echo "$XKBSETUP" | grep '^geometry' | awk '{ print $2 }'` if [ -n "$XKBKEYMAP" ]; then - setxkbmap -keymap "$XKBKEYMAP" + $SETXKBMAP -keymap "$XKBKEYMAP" elif [ -n "$XKBTYPES" -a -n "$XKBCOMPAT" -a -n "$XKBSYMBOLS" -a -n "$XKBGEOMETRY" ]; then - setxkbmap -types "$XKBTYPES" -compat "$XKBCOMPAT" -symbols "$XKBSYMBOLS" -geometry "$XKBGEOMETRY" + $SETXKBMAP -types "$XKBTYPES" -compat "$XKBCOMPAT" -symbols "$XKBSYMBOLS" -geometry "$XKBGEOMETRY" elif [ -n "$XKBTYPES" -a -n "$XKBCOMPAT" -a -n "$XKBSYMBOLS" ]; then - setxkbmap -types "$XKBTYPES" -compat "$XKBCOMPAT" -symbols "$XKBSYMBOLS" + $SETXKBMAP -types "$XKBTYPES" -compat "$XKBCOMPAT" -symbols "$XKBSYMBOLS" elif [ -n "$XKBSYMBOLS" ]; then - setxkbmap -symbols "$XKBSYMBOLS" + $SETXKBMAP -symbols "$XKBSYMBOLS" fi fi fi diff --git a/config/Makefile.am b/config/Makefile.am index 4db3cbd8..1e4bb289 100644 --- a/config/Makefile.am +++ b/config/Makefile.am @@ -30,7 +30,7 @@ EXTRA_DIST = \ gettextfoo.h \ extract-shell.sh -gettextfoo.h: XKeepsCrashing +gettextfoo.h: XKeepsCrashing Xsession.in cat $^ | $(srcdir)/extract-shell.sh > gettextfoo.h @INTLTOOL_DESKTOP_RULE@ diff --git a/config/PostSession.in b/config/PostSession.in index 75e54ae7..a139b7cb 100755 --- a/config/PostSession.in +++ b/config/PostSession.in @@ -1,8 +1,9 @@ #!/bin/sh -PATH=@X_PATH@:$PATH +PATH=@X_PATH@:$PATH:/bin:/usr/bin -if command -v sessreg > /dev/null 2>&1; then - sessreg -d -w /var/log/wtmp -u /var/run/utmp -x "$X_SERVERS" -h "$REMOTE_HOST" -l $DISPLAY $USER +SESSREG=`which sessreg 2>/dev/null` +if [ x$SESSREG != x ] ; then + $SESSREG -d -w /var/log/wtmp -u /var/run/utmp -x "$X_SERVERS" -h "$REMOTE_HOST" -l $DISPLAY $USER fi exit 0 diff --git a/config/PreSession.in b/config/PreSession.in index c1af766a..bf557be2 100755 --- a/config/PreSession.in +++ b/config/PreSession.in @@ -6,18 +6,21 @@ # # Note that output goes into the .xsession-errors file for easy debugging # -PATH=@X_PATH@:$PATH +PATH=@X_PATH@:$PATH:/bin:/usr/bin -if command -v xsetroot > /dev/null 2>&1; then - xsetroot -cursor_name left_ptr -solid "#363047" +XSETROOT=`which xsetroot 2>/dev/null` +if [ x$XSETROOT != x ] ; then + $XSETROOT -cursor_name left_ptr -solid "#363047" fi -if command -v sessreg > /dev/null 2>&1; then + +SESSREG=`which sessreg 2>/dev/null` +if [ x$SESSREG != x ] ; then # some output for easy debugging echo "$0: Registering your session with wtmp and utmp" - echo "$0: running: sessreg -a -w /var/log/wtmp -u /var/run/utmp -x \"$X_SERVERS\" -h \"$REMOTE_HOST\" -l $DISPLAY $USER" + echo "$0: running: $SESSREG -a -w /var/log/wtmp -u /var/run/utmp -x \"$X_SERVERS\" -h \"$REMOTE_HOST\" -l $DISPLAY $USER" - exec sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "$X_SERVERS" -h "$REMOTE_HOST" -l $DISPLAY $USER + exec $SESSREG -a -w /var/log/wtmp -u /var/run/utmp -x "$X_SERVERS" -h "$REMOTE_HOST" -l $DISPLAY $USER # this is not reached fi diff --git a/config/XKeepsCrashing b/config/XKeepsCrashing index ce0f0fe6..2b81b62a 100755 --- a/config/XKeepsCrashing +++ b/config/XKeepsCrashing @@ -1,12 +1,16 @@ #!/bin/sh -GTBIN=`which gettext` +if [ -x "$LIBEXECDIR/gdmtranslate" ] ; then + GDMTRANSLATE="$LIBEXECDIR/gdmtranslate" +else + GDMTRANSLATE= +fi gettextfunc () { - if test "x$GTBIN" = "x" ; then - echo "$1" + if [ "x$GDMTRANSLATE" != "x" ] ; then + $GDMTRANSLATE "$1" else - $GTBIN -s "$1" + echo "$1" fi } diff --git a/config/Xsession.in b/config/Xsession.in index 02d870f7..7979c2bf 100755 --- a/config/Xsession.in +++ b/config/Xsession.in @@ -33,7 +33,26 @@ test -f $HOME/.profile && . $HOME/.profile test -f /etc/xprofile && . /etc/xprofile test -f $HOME/.xprofile && . $HOME/.xprofile -zenity=`which zenity` +# Translation stuff +if [ -x "@EXPANDED_LIBEXECDIR@/gdmtranslate" ] ; then + gdmtranslate="@EXPANDED_LIBEXECDIR@/gdmtranslate" +else + gdmtranslate= +fi + +# Note that this should only go to zenity dialogs which always expect utf8 +gettextfunc () { + if [ "x$gdmtranslate" != "x" ] ; then + $gdmtranslate --utf8 "$1" + else + echo "$1" + fi +} + +zenity=`which zenity 2>/dev/null` +if [ -z "$zenity" ] ; then + echo "zenity not found!" +fi command="$1" @@ -43,7 +62,7 @@ fi if [ x"$command" = xfailsafe ] ; then if [ -n "$zenity" ] ; then - $zenity --info --text "This is the failsafe xterm session. Windows now have focus only if you have your cursor above them. To get out of this mode type \"exit\" in the window in the upper left corner" + $zenity --info --text `gettextfunc "This is the failsafe xterm session. Windows now have focus only if you have your cursor above them. To get out of this mode type 'exit' in the window in the upper left corner"` fi exec xterm -geometry 80x24+0+0 fi @@ -52,8 +71,9 @@ fi # works for ALL sessions (except ones named 'Failsafe') # clean up after xbanner -if which freetemp 2> /dev/null ; then - freetemp +freetemp=`which freetemp 2>/dev/null` +if [ -n "$freetemp" ] ; then + $freetemp fi userresources=$HOME/.Xresources @@ -125,12 +145,12 @@ unset XKB_IN_USE # Normalize languages, some places/distros screw us up in /etc/profile, # so in case the user did select a language if [ -n "$GDM_LANG" ]; then - LANG=$GDM_LANG + LANG="$GDM_LANG" export LANG if [ -n "$LC_ALL" ]; then if [ "$LC_ALL" != "$LANG" ]; then - LC_ALL=$LANG + LC_ALL="$LANG" fi else unset LC_ALL @@ -138,7 +158,7 @@ if [ -n "$GDM_LANG" ]; then if [ -n "$LANGUAGE" ]; then if [ "$LANGUAGE" != "$LANG" ]; then - LANGUAGE=$LANG + LANGUAGE="$LANG" fi else unset LANGUAGE @@ -146,7 +166,7 @@ if [ -n "$GDM_LANG" ]; then if [ -n "$LINGUAS" ]; then if [ "$LINGUAS" != "$LANG" ]; then - LINGUAS=$LANG + LINGUAS="$LANG" fi else unset LINGUAS @@ -186,9 +206,11 @@ if [ "x$command" = "xdefault" ] ; then fi # add ssh-agent if found -sshagent=`which ssh-agent` +sshagent=`which ssh-agent 2>dev/null` if [ -n "$sshagent" ] && [ -x "$sshagent" ] && [ -z "$SSH_AUTH_SOCK" ]; then command="$sshagent -- $command" +elif [ -z "$sshagent" ] ; then + echo "ssh-agent not found!" fi echo "Xsession: Setup done, will execute: $command" @@ -198,7 +220,7 @@ eval exec $command echo "Xsession: Executing $command failed, will run xterm" if [ -n "$zenity" ] ; then - $zenity --info --text "I could not start your session and so I have started the failsafe xterm session. Windows now have focus only if you have your cursor above them. To get out of this mode type \"exit\" in the window in the upper left corner" + $zenity --info --text `gettextfunc "I could not start your session and so I have started the failsafe xterm session. Windows now have focus only if you have your cursor above them. To get out of this mode type 'exit' in the window in the upper left corner"` fi exec xterm -geometry 80x24+0+0 diff --git a/config/gettextfoo.h b/config/gettextfoo.h index 8392cef1..cb3dfd35 100644 --- a/config/gettextfoo.h +++ b/config/gettextfoo.h @@ -9,3 +9,5 @@ const char *foo = N_("I cannot start the X server (your graphical interface). I const char *foo = N_("Would you like to view the detailed X server output as well?"); const char *foo = N_("I cannot start the X server (your graphical interface). It seems that the pointer device (your mouse) is not set up correctly. Would you like to view the X server output to diagnose the problem?"); const char *foo = N_("Would you like me to try to run the mouse configuration program? Note that you will need the root password for this."); +const char *foo = N_("This is the failsafe xterm session. Windows now have focus only if you have your cursor above them. To get out of this mode type 'exit' in the window in the upper left corner"); +const char *foo = N_("I could not start your session and so I have started the failsafe xterm session. Windows now have focus only if you have your cursor above them. To get out of this mode type 'exit' in the window in the upper left corner"); diff --git a/configure.in b/configure.in index bd89aff9..0e1b540c 100644 --- a/configure.in +++ b/configure.in @@ -277,11 +277,19 @@ if test x$enable_authentication_scheme != xcrypt -a \ fi GDMASKPASS= +EXTRA_GDMASKPASS_LIBS= if test x$have_pam = xyes ; then AC_CHECK_HEADERS(security/pam_misc.h, [ GDMASKPASS=gdmaskpass]) + if test x$GDMASKPASS != x ; then + AC_CHECK_LIB(pam,misc_conv,,[AC_CHECK_LIB(pam_misc,misc_conv, [ + EXTRA_GDMASKPASS_LIBS="$EXTRA_GDMASKPASS_LIBS -lpam_misc"], [ + GDMASKPASS=], [ + -lpam])]) + fi fi AC_SUBST(GDMASKPASS) +AC_SUBST(EXTRA_GDMASKPASS_LIBS) if test x$enable_authentication_scheme = xpam -a x$have_pam = xno ; then AC_MSG_ERROR(PAM support requested but not available) @@ -557,6 +565,7 @@ config/Makefile po/Makefile.in vicious-extensions/Makefile docs/Makefile +docs/C/Makefile config/gdm.conf config/Xsession config/Default diff --git a/daemon/misc.c b/daemon/misc.c index 58ba7726..df6453e2 100644 --- a/daemon/misc.c +++ b/daemon/misc.c @@ -26,6 +26,8 @@ #include <sys/wait.h> #include <sys/socket.h> #include <sys/ioctl.h> +#include <sys/time.h> +#include <sys/resource.h> #include <fcntl.h> #include <netinet/in.h> #include <net/if.h> diff --git a/daemon/slave.c b/daemon/slave.c index d1ace176..9a749c28 100644 --- a/daemon/slave.c +++ b/daemon/slave.c @@ -2615,7 +2615,8 @@ session_child_run (struct passwd *pwent, if (setusercontext (NULL, pwent, pwent->pw_uid, LOGIN_SETLOGIN | LOGIN_SETPATH | LOGIN_SETPRIORITY | LOGIN_SETRESOURCES | - LOGIN_SETUMASK | LOGIN_SETUSER) < 0) + LOGIN_SETUMASK | LOGIN_SETUSER | + LOGIN_SETENV) < 0) gdm_child_exit (DISPLAY_REMANAGE, _("%s: setusercontext() failed for %s. " "Aborting."), "gdm_slave_session_start", diff --git a/docs/C/Makefile.am b/docs/C/Makefile.am index 92c87f9d..8b2c09bd 100644 --- a/docs/C/Makefile.am +++ b/docs/C/Makefile.am @@ -1,38 +1,7 @@ -gdm_helpdir = $(datadir)/gnome/help/gdm/C - -gdm_help_DATA = \ - gdm.html - -SGML_FILES = gdm.sgml - -EXTRA_DIST = \ - $(SGML_FILES) - -all: - -gdm.html: gdm/index.html - -cd $(srcdir) && cp gdm/index.html gdm.html - -gdm/index.html: $(SGML_FILES) - -cd $(srcdir) && db2html gdm.sgml - -dist-hook: - mkdir $(distdir)/gdm - -cp $(srcdir)/gdm/*.html gdm/*.css $(distdir)/gdm - -cp $(srcdir)/gdm.html $(distdir) - -cp $(srcdir)/gdm.html $(distdir)/gdm/index.html - -install-data-local: gdm.html - $(mkinstalldirs) $(DESTDIR)$(gdm_helpdir)/images - -for file in $(srcdir)/gdm/*.html $(srcdir)/gdm/*.css; do \ - basefile=`basename $$file`; \ - $(INSTALL_DATA) $$file $(DESTDIR)$(gdm_helpdir)/$$basefile; \ - done - $(INSTALL_DATA) $(srcdir)/gdm.html $(DESTDIR)$(gdm_helpdir)/index.html - -gdm.ps: $(SGML_FILES) - db2ps $< - -gdm.rtf: $(SGML_FILES) - -db2rtf $< - +figdir = +docname = gdm +lang = C +omffile = gdm-C.omf +entities = legal.xml +include $(top_srcdir)/xmldocs.make +dist-hook: app-dist-hook diff --git a/docs/C/gdm.sgml b/docs/C/gdm.sgml deleted file mode 100644 index 0a5403cc..00000000 --- a/docs/C/gdm.sgml +++ /dev/null @@ -1,1925 +0,0 @@ -<!DOCTYPE book PUBLIC "-//Davenport//DTD DocBook V3.0//EN" []> - -<book id="index"> - <bookinfo> - <title>Gnome Display Manager Reference Manual</title> - <authorgroup> - <author> - <firstname>Martin</firstname><othername>K.</othername><surname>Petersen</surname> - <affiliation> - <address><email>mkp@mkp.net</email></address> - </affiliation> - </author> - <author> - <firstname>George</firstname><surname>Lebl</surname> - <affiliation> - <address><email>jirka@5z.com</email></address> - </affiliation> - </author> - <author> - <firstname>Tim</firstname><surname>Jansen</surname> - <affiliation> - <address><email>tim@tjansen.de</email></address> - </affiliation> - </author> - </authorgroup> - <copyright> - <year>1998, 1999</year> <holder>Martin K. Petersen</holder> - </copyright> - <copyright> - <year>2001</year> <holder>Tim Jansen</holder> - </copyright> - <copyright> - <year>2001</year> <holder>George Lebl</holder> - </copyright> - - <legalnotice> - <para> - This documentation is free software; you can redistribute it - and/or modify it under the terms of the GNU General Public - License as published by the Free Software Foundation; either - version 2 of the License, or (at your option) any later - version. - </para> - - <para> - This program is distributed in the hope that it will be - useful, but WITHOUT ANY WARRANTY; without even the implied - warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR - PURPOSE. See the GNU General Public License for more details. - </para> - - <para> - You should have received a copy of the GNU General Public - License along with this program; if not, write to the Free - Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, - MA 02111-1307 USA - </para> - - <para> - For more details see the file COPYING in the source - distribution of GDM. - </para> - </legalnotice> - </bookinfo> - - <toc></toc> - - <preface> - <title>Terms and conventions used in this book</title> - - <para> - GDM - Gnome Display Manager. Used to describe the software - package as a whole. - </para> - - <para> - gdm - The Gnome Display Manager daemon (<filename>gdm</filename>). - </para> - - <para> - Greeter - The graphical login window (<filename>gdmlogin</filename>). - </para> - - <para> - Chooser - The host chooser which appears on remote displays - sending INDIRECT queries (<filename>gdmchooser</filename>). - </para> - - <para> - Configurator - The configuration program (<filename>gdmconfig</filename>). - </para> - - <para> - Paths without a leading '/' are relative to the installation - prefix. I.e. <filename>share/pixmaps/</filename> refers to - <filename>/usr/share/pixmaps</filename> if GDM was configured - with <filename>--prefix=/usr</filename>. - </para> - - </preface> - - <chapter id="intro"> - <title>Overview</title> - - <sect1> - <title> - Introduction - </title> - - <para> - GDM is a replacement for XDM, the X Display Manager. Unlike its - competitors (X3DM, KDM, WDM) GDM was written from scratch and - does not contain any original XDM / X Consortium code. - </para> - </sect1> - - <sect1 id="daemonov"> - <title>The GDM Daemon</title> - - <para> - GDM was written with simplicity and security in mind. The - overall design concept is this: - </para> - - <para> - Upon startup the <filename>gdm</filename> daemon parses its config file - <filename>gdm.conf</filename>. For each of the local displays <filename>gdm</filename> - forks an Xserver and a slave process. The main <filename>gdm</filename> process - will then listen to XDMCP requests from remote displays and - monitor the local display sessions. - </para> - - <para> - The <filename>gdm</filename> slave process opens the display and starts - <filename>gdmlogin</filename>, the graphical login - program. <filename>gdmlogin</filename> runs as a dedicated - user and communicates asynchronously with the slave process - through a pipe. - </para> - - <para> - GDM relies heavily on the presence of PAM, Pluggable - Authentication Modules, but supports regular crypt() - and shadow passwords on legacy systems. - </para> - - <para> - Remote displays can connect to the XDMCP port on the GDM - host. <filename>gdm</filename> will grant access to hosts specified in - the gdm service section in your TCP Wrappers configuration - file. GDM does not support remote display access control on - systems without TCP Wrappers. XDMCP support can be turned off - completely, however. - </para> - - <para> - GDM includes several measures making it more resistant to - denial of service attacks on the XDMCP service. A lot of the - protocol parameters, handshaking timeouts etc. can be fine - tuned. The defaults should work for most systems, however. - Don't change them unless you know what you're doing. - </para> - - <para> - In general GDM is very reluctant regarding reading/writing of - user files. For instance it refuses to touch anything but - regular files. Links, sockets and devices are ignored. The - value of the RelaxPermissions parameter determines whether GDM - should accept files writable by the user's group or others. - These are ignored by default. - </para> - - <para> - All operations on user files are done with the effective - userid of the user. If the sanity check fails on the user's - <filename>.Xauthority</filename> file, a fallback cookie is created in - <filename>/tmp</filename>. - </para> - - <para> - Finally, the sysadmin can specify the maximum file size GDM - should accept, and, if the face browser is enabled, a tunable - maximum icon size is also enforced. On large systems it is - still advised to turn off the face browser for performance - reasons. Looking up icons in homedirs, scaling and rendering - face icons can take quite a long time. YMMV. - </para> - </sect1> - - <sect1> - <title> - XDMCP - </title> - - <para> - GDM also supports the X Display Manager Protocol (XDMCP) for - managing remote displays. - </para> - - <para> - GDM listens to UDP port 177 and will repond to QUERY and - BROADCAST_QUERY requests by sending a WILLING packet to the - originator. - </para> - - <para> - GDM can also be configured to honor INDIRECT queries and - present a host chooser to the remote display. GDM will - remember the user's choice and forward subsequent requests to - the chosen manager. - </para> - - <para> - GDM only supports the MIT-MAGIC-COOKIE-1 authentication - system. Little is gained from the other schemes, and no - effort has been made to implement them so far. - </para> - - <para> - Since it is fairly easy to do denial of service attacks on the - XDMCP service, GDM incorporates a few features to guard - against attacks. Please read the XDMCP reference section below - for more information. - </para> - - <para> - Even though GDM tries to outsmart potential attackers, it is - still adviced that you block UDP port 177 on your firewall - unless you really need it. GDM guards against DoS attacks, but - the X protocol is still inherently insecure and should only be - used in controlled environments. - </para> - - <para> - Even though your display is protected by cookies the XEvents - and thus the keystrokes typed when entering passwords will - still go over the wire in clear text. It is trivial to capture - these. You should also be aware that cookies, if placed on an - NFS mounted directory, are prone to eavesdropping too. - </para> - - </sect1> - - <sect1> - <title>The Greeter</title> - - <para> - The greeter is the graphical user interface that is presented - to the user. The greeter contains a menu at the top, an - optional face browser, an optional logo and a text entry - widget. - </para> - - <sect2> - <title> - Text entry - </title> - - <para> - The text entry field is used for entering logins, passwords, - passphrases etc. <filename>gdmlogin</filename> is controlled by the - underlying daemon and is basically stateless. The daemon - controls the greeter through a simple protocol where it can - ask the greeter for a text string with echo turned on or - off. Similarly, the daemon can change the label above the - text entry widget to correspond to the value the - authentication system wants the user to enter. - </para> - - </sect2> - - <sect2> - <title> - The Menu - </title> - - <para> - The menu bar in the top of the greeter enables the user to - select the requested session type/desktop environment, - select an appropriate locale/language and optionally - shutdown/reboot the machine. The greeter window can also be - iconified to make room for other applications on the login - screen. - </para> - - </sect2> - - <sect2> - <title> - The face browser - </title> - - <para> - The greeter provides a face browser containing icons for all - the users on a system. The icons can be installed globally - by the sysadmin or in the users' home directories. - </para> - - <para> - Face icons placed in the global face directory - must be readable to the gdm user. However, the daemon, proxies - user pictures to the greeter and thus those don't have be be - readable by the gdm user, but root. - </para> - - <para> - Please note that loading and scaling face icons located in - user home directories can be a very time consuming task. - Especially on large systems or systems running NIS. The - browser feature is only intended for systems with relatively - few users. - </para> - - <para> - To filter out unwanted user names in the browser, an exclude - option is implemented. The greeter will automatically ignore - usernames listed in the <filename>Exclude</filename> statement in the - config file. - </para> - - <para> - When the browser is turned on, valid usernames on the - machine are inherently exposed to a potential intruder. If - your system is connected directly to the Internet, this - might be a bad idea. - </para> - - </sect2> - - <sect2> - <title> - The Logo - </title> - - <para> - The greeter can optionally display a logo in the login - window. The image must be in a format readable to the Imlib - library (GIF, JPG, PNG, TIFF, XPM and possibly others), and - it must be readable to the gdm user. See the <filename> - Logo</filename> option in the reference section below for detauls. - </para> - - </sect2> - - </sect1> - - </chapter> - - <chapter id="Configuration"> - <title>The Configuration Directory</title> - - <para> - This chapter will cover the structure of the configuration - directory and the format of the configuration file. However you - can use the <filename>gdmconfig</filename> binary to configure - GDM from a graphical environment. The terms from this chapter - could however still come in handy. If you want to run the - configurator from the GNOME menu, it should be installed under - the <filename>System</filename> submenu. - </para> - - <para> - The configuration files for GDM are located in the - <filename>etc/gdm/</filename> directory. - </para> - - <para> - This is a listing of the config directory contents: - </para> - - <screen> - Init/ - PostSession/ - PreSession/ - Sessions/ - gdm.conf - </screen> - - <para> - <filename>gdm.conf</filename> is the main GDM configuration file. The - options will be described later in this chapter. - </para> - - <para> - <filename>gdm.conf</filename> is configuration file for both <filename> - gdm</filename>, <filename>gdmlogin</filename>, and <filename>gdmchooser</filename> since a - lot of parameters overlap. - </para> - - <para> - The remaining configuration is done by dropping scripts in the - subdirectories of the <filename>etc/gdm</filename> folder. This - approach makes it easy for package management systems to install - window managers and different session types without requiring - the sysadmin to edit files. - </para> - - <sect1> - <title>The Script Directories</title> - - <para> - In this section we will explain the <filename>Init</filename>, - <filename>PreRoot</filename> and <filename>PostRoot</filename> directories as - they are very similar. - </para> - - <para> - When the X server has been successfully started, GDM will try - to run the script called - <filename>Init/<displayname></filename>. I.e. <filename>Init/:0</filename> - for the first local display. If this file is not found, GDM - will attempt to to run <filename>Init/Default</filename>. The - script will be run as root and GDM blocks until it - terminates. Use the <filename>Init/*</filename> script for - programs that are supposed to run alongside with the GDM login - window. xconsole for instance. Commands to set the background - etc. goes in this file too. - </para> - - <para> - It is up to the sysadmin to decide whether clients started by - the Init script should be killed before starting the user - session. This is controlled with the KillInitClients option in - <filename>gdm.conf</filename>. - </para> - - <para> - When the user has been successfully authenticated, GDM tries - to run the PreSession script. Similar to the Init-scripts, - <filename>PreSession/<displayname></filename> will be - executed, if this file doesn't exist, GDM will attempt to run - <filename>PreSession/Default</filename>. The script will be - run as root and GDM blocks until it terminates. Use this - script for local session management or accounting stuff. The - $USER environment variable contains the login of the - authenticated user. The script should return 0 on success. Any - other value will cause GDM to terminate the current login - process. - </para> - - <para> - Then the session script is run. Session scripts are located in - the <filename>etc/gdm/Session</filename> directory. Which one - GDM runs, depends on the session the user chose in the - Sessions-menu in the greeter. If no session is selected and - the user has no last session stored in his - <filename>~/.gnome/gdm</filename> file, the system will choose - or first script found or -- if - <filename>Sessions/Default</filename> exists -- this will be - run. For instance you can create a symlink from - <filename>Gnome</filename> to <filename>Default</filename> to - make Gnome the default desktop environment. - </para> - - <para> - When the user terminates his session, the PostSession script - will be run. Operation is similar to Init and PreSession. That - is, GDM will attempt to execute the script - <filename>PostSession/<displayname></filename> and if - that doesn't exist <filename>PostSession/Default</filename> - will be run. Again the script will be run with root - priviledges, the slave daemon will block and the $USER - environment variable will contain the name of the user who - just logged out. - </para> - - <para> - 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. - </para> - - <para> - Neither of the Init, PreSession or PostSession scripts are - necessary and can be left out. At least one session script is - required for proper operation. - </para> - - </sect1> - - <sect1> - <title>The Configuration File - <filename>gdm.conf</filename></title> - - <para> - The daemon and the accompanying utilities share a common - configuration file: <filename>etc/gdm/gdm.conf</filename>. - </para> - - <para> - The configuration file is divided into sections each - containing variables that define the behaviour for a specific - part of the GDM suite. - </para> - - <para> - <filename>gdm.conf</filename> follows the standard GNOME configuration - file syntax. Keywords in brackets define sections, strings - before an equal sign (=) are variables and the data after - equal sign represents their value. - </para> - - <sect2> - <title>Daemon Configuration</title> - - <variablelist> - <title>[daemon]</title> - - <varlistentry> - <term>AlwaysRestartServer</term> - <listitem> - <synopsis>AlwaysRestartServer=false</synopsis> - <para> - If true, then gdm never tries to reuse existing X servers by - reinitializing them. It will just kill the existing server and - start over. Normally, just reinitializing is a nicer way to go - but if the X server memory usage keeps growing this may be - a safer option. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>AutomaticLoginEnable</term> - <listitem> - <synopsis>AutomaticLoginEnable=false</synopsis> - <para> - If the user given in AutomaticLogin should be logged in upon - first bootup. No password will be asked. This is useful - for single user workstations where local console security - is not an issue. Also could be useful for public terminals, - although there see TimedLogin. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>AutomaticLogin</term> - <listitem> - <synopsis>AutomaticLogin=</synopsis> - <para> - This user should be automatically logged in on first bootup. - AutomaticLoginEnable must be true and this must be - a valid user for this to happen. "root" can never be - autologged in however and gdm will just refuse to do it even - if you set it up. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Chooser</term> - <listitem> - <synopsis>Chooser=bin/gdmchooser --disable-sound --disable-crash-dialog</synopsis> - <para> - Full path and name of the chooser executable followed by optional arguments. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Configurator</term> - <listitem> - <synopsis>Configurator=bin/gdmconfig --disable-sound --disable-crash-dialog</synopsis> - <para> - The pathname to the configurator binary. If the greeter - ConfigAvailable option is set to true then run this binary - when somebody chooses Configuration from the system menu. - Of course GDM will first ask for root password however. - And it will never allow this to happen from a remote display. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>DefaultPath</term> - <listitem> - <synopsis>DefaultPath=/bin:/usr/bin:/usr/bin/X11:/usr/local/bin</synopsis> - <para> - Specifies the path which will be set in the user's session. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>DisplayInitDir</term> - <listitem> - <synopsis>DisplayInitDir=etc/gdm/Init</synopsis> - <para> - Directory containing the display init scripts. See the - ``Script Directories'' section for more info. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>FailsafeXServer</term> - <listitem> - <synopsis>FailsafeXServer=</synopsis> - <para> - An X command line in case we can't start the normal X server. - should probably be some sort of a script that runs an - appropriate low resolution server that will just work. - This is tried before the XKeepsCrashing script is run. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>FlexibleXServers</term> - <listitem> - <synopsis>FlexibleXServers=5</synopsis> - <para> - The maximum number of allowed flexible servers. These are - servers that can be run using the /tmp/.gdm_socket socket - connection. This is used for both full servers and for - Xnest servers. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>GnomeDefaultSession</term> - <listitem> - <synopsis>GnomeDefaultSession=share/gnome/default.session</synopsis> - <para> - The filename which GDM should read if there is no per user - GNOME session file, and the user has requested the Gnome - Chooser session. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Greeter</term> - <listitem> - <synopsis>Greeter=bin/gdmlogin --disable-sound --disable-crash-dialog</synopsis> - <para> - Full path and name of the greeter executable followed by optional arguments. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Group</term> - <listitem> - <synopsis>Group=gdm</synopsis> - <para> - The group id under which - <filename>gdmlogin</filename>/<filename>gdmchooser</filename> - are run. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>HaltCommand</term> - <listitem> - <synopsis>HaltCommand=/sbin/shutdown -h now</synopsis> - <para> - Full path and arguments to command to be executed when - user selects Halt from the System menu. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>KillInitClients</term> - <listitem> - <synopsis>KillInitClients=true</synopsis> - <para> - Determines whether GDM should kill X clients started by - the init scripts when the user logs in. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>LogDir</term> - <listitem> - <synopsis>LogDir=var/gdm</synopsis> - <para> - Directory containing the log files for the individual - displays. By default this is the same as the - ServAuthDir. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>PidFile</term> - <listitem> - <synopsis>PidFile=var/run/gdm.pid</synopsis> - <para> - Name of the file containing the <filename>gdm</filename> - process id. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>PostSessionScriptDir</term> - <listitem> - <synopsis>PostSessionScriptDir=etc/gdm/PostSession</synopsis> - <para> - Directory containing the scripts run after the user logs - out. See the ``Script Directories'' section for more - info. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>PreSessionScriptDir</term> - <listitem> - <synopsis>PreSessionScriptDir=etc/gdm/PreSession</synopsis> - <para> - Directory containing the scripts run before the user - logs in. See the ``Script Directories'' section for - more info. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>RebootCommand</term> - <listitem> - <synopsis>RebootCommand=/sbin/shutdown -r now</synopsis> - <para> - Full path and optional arguments to the program to be - executed when user selects Reboot from the System menu. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>RootPath</term> - <listitem> - <synopsis>RootPath=/sbin:/usr/sbin:/bin:/usr/bin:/usr/bin/X11:/usr/local/bin</synopsis> - <para> - Specifies the path which will be set in the root's - session and the {Init,PreSession,PostSession} scripts - executed by GDM. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ServAuthDir</term> - <listitem> - <synopsis>ServAuthDir=/var/gdm</synopsis> - <para> - Directory containing the X authentication files for the - individual displays. Should be owned by - <filename>gdm.gdm</filename> with permissions 750. - This directory is also used for other private files that - the daemon needs to store. Other user should not - have any way to get into this directory and read/change - it's contents. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>SessionDir</term> - <listitem> - <synopsis>SessionDir=etc/gdm/Sessions</synopsis> - <para> - Directory containing the scripts for all session types - available on the system. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>StandardXServer</term> - <listitem> - <synopsis>StandardXServer=/usr/bin/X11/X</synopsis> - <para> - Full path and arguments to the standard X server command. - This is used when gdm cannot find any other definition, - and it's used as the default and failsafe fallback in a - number of places. This should be able to run some sort - of X server. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>SuspendCommand</term> - <listitem> - <synopsis>SuspendCommand=</synopsis> - <para> - Full path and arguments to command to be executed when - user selects Suspend from the System menu. If empty - there is no such menu item. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>TimedLoginEnable</term> - <listitem> - <synopsis>TimedLoginEnable=false</synopsis> - <para> - 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 public 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, whichever is higher. Note that - no password will be asked for this user so you should be - careful. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>TimedLogin</term> - <listitem> - <synopsis>TimedLogin=</synopsis> - <para> - This is the user that should be logged in after a specified - number of seconds of inactivity. This can never be "root" - and gdm will refuse to log in root this way. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>TimedLoginDelay</term> - <listitem> - <synopsis>TimedLoginDelay=30</synopsis> - <para> - This is the delay before the TimedLogin user will be logged - in. It must be greater then or equal to 10. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>User</term> - <listitem> - <synopsis>User=gdm</synopsis> - <para> - The username under which <filename>gdmlogin</filename> / - <filename>gdmchooser</filename> are run. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>UserAuthDir</term> - <listitem> - <synopsis>UserAuthDir=</synopsis> - <para> - The directory where user's - <filename>.Xauthority</filename> file should be - saved. When nothing is specfied the user's home - directory is used. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>UserAuthFBDir</term> - <listitem> - <synopsis>UserAuthFBDir=/tmp</synopsis> - <para> - If GDM fails to update the user's - <filename>.Xauthority</filename> file a - fallback cookie is created in this directory. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>UserAuthFile</term> - <listitem> - <synopsis>UserAuthFile=.Xauthority</synopsis> - <para> - Name of the file used for storing user cookies. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>XKeepsCrashing</term> - <listitem> - <synopsis>XKeepsCrashing=etc/gdm/XKeepsCrashing</synopsis> - <para> - A script to run in case X keeps crashing. This is for running - An X configuration or whatever else to make the X configuration - work. See the script that came with the distribution for an - example. The distributed XKeepsCrashing script is tested - on RedHat, but may work elsewhere. Your system integrator should - make sure this script is up to date for your particular system. - </para> - <para> - In case FailsafeXServer is setup, that will be tried first. - and this only used as a backup if even that server keeps - crashing. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Xnest</term> - <listitem> - <synopsis>Xnest=/usr/bin/X11/Xnest</synopsis> - <para> - The full path and arguments to the Xnest command. This is used - for the flexible Xnest servers. This way the user can start new - login screens in a nested window. Of course you must have the Xnest - server from your X server packages installed for this to work. - </para> - </listitem> - </varlistentry> - </variablelist> - - </sect2> - - <sect2> - <title>Security Options</title> - - <variablelist> - <title>[security]</title> - - <varlistentry> - <term>AllowRoot</term> - <listitem> - <synopsis>AllowRoot=true</synopsis> - <para> - Allow root (privilaged user) to log in through GDM. Set - this to false if you want to disallow such logins. - </para> - <para> - On systems that support PAM, this parameter is - not as useful as you can use PAM to do the same thing, - and in fact do even more. However it is still followed, - so you should probably leave it true for PAM systems. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>AllowRemoteRoot</term> - <listitem> - <synopsis>AllowRemoteRoot=true</synopsis> - <para> - Allow root (privilaged user) to log in remotely through GDM. - Set this to false if you want to disallow such logins. Remote - logins are any logins that come in through the xdmcp. - </para> - <para> - On systems that support PAM, this parameter is - not as useful as you can use PAM to do the same thing, - and in fact do even more. However it is still followed, - so you should probably leave it true for PAM systems. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>AllowRemoteAutoLogin</term> - <listitem> - <synopsis>AllowRemoteAutoLogin=false</synopsis> - <para> - Allow the timed login to work remotely. That is, remote - connections through XDMCP will be allowed to log into the - "TimedLogin" user by letting the login window time out, just - like the local user on the first console. - </para> - <para> - Note that this can make a system quite insecure, and thus is - off by default. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>RelaxPermissions</term> - <listitem> - <synopsis>RelaxPermissions=0</synopsis> - <para> - By default GDM ignores files and directories writable to - other users than the owner. - </para> - - <para> - Changing the value of RelaxPermissions makes it - possible to alter this behaviour: - </para> - - <para> - 0 - Paranoia option. Only accepts user owned files and directories. - </para> - <para> - 1 - Allow group writable files and directories. - </para> - <para> - 2 - Allow world writable files and directories. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>RetryDelay</term> - <listitem> - <synopsis>RetryDelay=3</synopsis> - <para> - The number of seconds GDM should wait before - reactivating the entry field after a failed login. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>SessionMaxFile</term> - <listitem> - <synopsis>SessionMaxFile=524288</synopsis> - <para> - GDM will refuse to read session files bigger than this - number (specified in bytes). This can be bigger then - UserMaxFile, since these are never read into memory, and - so it is harder to "attack" gdm in this way. - </para> - - <para> - In addition to the size check both - <filename>gdm</filename> and - <filename>gdmlogin</filename> are extremely picky - about accessing files in user directories. Neither - will follow symlinks and they can optionally refuse to - read files and directories writable by other than the - owner. See the RelaxPermissions option for more info. - </para> - - <para> - However for the session files, GDM is not as picky. If you - set RelaxPermissions to 0, GDM will assume it to be 1 for - the case of session files. This is unfortunately because - the session files would then never be able to be read in. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>UserMaxFile</term> - <listitem> - <synopsis>UserMaxFile=65536</synopsis> - <para> - GDM will refuse to read/write files bigger than this number - (specified in bytes). - </para> - - <para> - In addition to the size check both - <filename>gdm</filename> and - <filename>gdmlogin</filename> are extremely picky - about accessing files in user directories. Neither - will follow symlinks and they can optionally refuse to - read files and directories writable by other than the - owner. See the RelaxPermissions option for more info. - </para> - </listitem> - </varlistentry> - </variablelist> - - </sect2> - - <sect2> - <title>XDCMP Support</title> - - <variablelist> - <title>[xdmcp]</title> - - <varlistentry> - <term>DisplaysPerHost</term> - <listitem> - <synopsis>DisplaysPerHost=1</synopsis> - <para> - To prevent attackers from filling up the pending - queue, GDM will only allow one connection for each - remote machine. If you want to provide display - services to machines with more than one screen, you - should increase the DisplaysPerHost value accordingly. - </para> - - <para> - Note that the number of connections from the local - machine is unlimited. Only remote connections - are limited by this number. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Enable</term> - <listitem> - <synopsis>Enable=false</synopsis> - <para> - Setting this to true enables XDMCP support allowing remote displays/X - terminals to be managed by GDM. - </para> - - <para> - <filename>gdm</filename> listens for requests on UDP - port 177. See the Port option for more information. - </para> - - <para> - If GDM is compiled to support it, access from remote displays - can be controlled using the TCP Wrappers library. The service name is - <filename>gdm</filename> - </para> - - <para> - You should add - </para> - - <screen> - gdm: .my.domain - </screen> - - <para> - to your <filename>/etc/hosts.allow</filename>. See the - <filename>hosts_access(5)</filename> man page for details. - </para> - - <para> - Please note that XDMCP is not a particularly secure protocol - and that it is a good idea to block UDP port 177 on your - firewall unless you really need it. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>HonorIndirect</term> - <listitem> - <synopsis>HonorIndirect=true</synopsis> - <para> - Enables XDMCP INDIRECT choosing (i.e. remote execution - of <filename>gdmchooser</filename>) for X-terminals - which don't supply their own display browser. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MaxPending</term> - <listitem> - <synopsis>MaxPending=4</synopsis> - <para> - To avoid denial of service attacks, GDM has fixed size - queue of pending connections. Only MaxPending displays - can start at the same time. - </para> - - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MaxPendingIndirect</term> - <listitem> - <synopsis>MaxPendingIndirect=4</synopsis> - <para> - GDM will only provide MaxPendingIndirect displays with - host choosers simultaneously. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MaxSessions</term> - <listitem> - <synopsis>MaxSessions=16</synopsis> - <para> - Determines the maximum number of remote display - connections which will be managed - simultaneously. I.e. the total number of remote displays - that can use your host. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MaxWait</term> - <listitem> - <synopsis>MaxWait=30</synopsis> - <para> - 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. - </para> - - <para> - GDM will then place the session id in the pending queue - waiting for the display to respond with a MANAGE request. - </para> - - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MaxWaitIndirect</term> - <listitem> - <synopsis>MaxWaitIndirect=30</synopsis> - <para> - 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 removed and the indirect - slot freed up for under displays. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Port</term> - <listitem> - <synopsis>Port=177</synopsis> - <para> - The UDP port number <filename>gdm</filename> should - listen to for XDMCP requests. Don't change this unless - you know what you're doing. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>PingIntervalSeconds</term> - <listitem> - <synopsis>PingIntervalSeconds=15</synopsis> - <para> - Interval in which to ping the X server in seconds. If the - X server doesn't return 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Willing</term> - <listitem> - <synopsis>Willing=etc/gdm/Xwilling</synopsis> - <para> - When the server 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 customized - message. If this script doesn't 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 server with QUERY packets. - </para> - </listitem> - </varlistentry> - </variablelist> - - </sect2> - - <sect2> - <title>Common GUI Configuration Options</title> - - <variablelist> - <title>[gui]</title> - - <varlistentry> - <term>Gtkrc</term> - <listitem> - <synopsis>Gtkrc=</synopsis> - <para> - Path to a <filename>gtkrc</filename> containing the - theme for use in <filename>gdmlogin</filename> / - <filename>gdmchooser</filename>. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MaxIconWidth</term> - <listitem> - <synopsis>MaxIconWidth=128</synopsis> - <para> - Specifies the maximum icon width (in pixels) that the - face browser will display. Icons larger than this will - be scaled. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MaxIconHeight</term> - <listitem> - <synopsis>MaxIconHeight=128</synopsis> - <para> - Specifies the maximum icon height (in pixels) that the - face browser will display. Icons larger than this will - be scaled. - </para> - </listitem> - </varlistentry> - </variablelist> - - </sect2> - - <sect2> - - <title>Greeter Configuration</title> - - <variablelist> - <title>[greeter]</title> - - <varlistentry> - <term>Browser</term> - <listitem> - <synopsis>Browser=true</synopsis> - <para> - Set to true to enable the face browser. See the ``Greeter'' - section for more information on the face browser. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ConfigAvailable</term> - <listitem> - <synopsis>ConfigAvailable=true</synopsis> - <para> - Allow the configurator to be run from the greeter. Note that - the user will need to type in the root password before the - configurator is run however. See the Configurator option - in the daemon section. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>DefaultFace</term> - <listitem> - <synopsis>DefaultFace=share/pixmaps/nophoto.png</synopsis> - <para> - Default icon file for users without a personal picture - in <filename>~/gnome/photo</filename>. The image must be - in an Imlib supported format and the file must be - readable for the gdm user. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>DefaultLocale</term> - <listitem> - <synopsis>DefaultLocale=english</synopsis> - <para> - This language is used for the session unless nothing is - specified in <filename>~user/.gnome/gdm</filename> and - the user didn't select a language in the Locale menu in - the greeter. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Exclude</term> - <listitem> - <synopsis>Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,...</synopsis> - <para> - Comma-separated list of usernames to exclude from the - face browser. The excluded users will still be able to - log in. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Font</term> - <listitem> - <synopsis>Font=-adobe-helvetica-bold-r-normal-*-*-180-*-*-*-*-*-*</synopsis> - <para> - Font to use for the welcome message in the greeter. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>GlobalFaceDir</term> - <listitem> - <synopsis>GlobalFaceDir=share/faces/</synopsis> - <para> - Systemwide directory for face files. The sysadmin can - place icons for users here without touching their - homedirs. Faces are named after their users' logins. - </para> - - <para> - I.e. <filename><GlobalFaceDir>/johndoe</filename> - would contain the face icon for the user ``johndoe''. No - image format extension should be specified. - </para> - - <para> - The face images must be stored in Imlib supported formats and - they must be readable for the GDM user. - </para> - - <para> - A user's own icon file will always take precedence over the sysadmin - provided one. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Icon</term> - <listitem> - <synopsis>Icon=share/pixmaps/gdm.xpm</synopsis> - <para> - Icon to use for <filename>gdmlogin</filename> when it's - in the iconified state. The image must be in an Imlib - supported format and it must be readable for the GDM - user. If no file is specified the iconify feature is - disabled. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>LocaleFile</term> - <listitem> - <synopsis>LocaleFile=etc/gdm/locale.alias</synopsis> - <para> - File in GNU locale format with entries for all supported - languages on the system. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Logo</term> - <listitem> - <synopsis>Logo=share/pixmaps/gnome-logo-large.png</synopsis> - <para> - Image file to display in the logo box. The file must be - in an Imlib supported format and it must be readable by - the GDM user. If no file is specified the logo feature - is disabled. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Quiver</term> - <listitem> - <synopsis>Quiver=true</synopsis> - <para> - Controls whether <filename>gdmlogin</filename> should - shake the display when an incorrect username/password is - entered. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>SystemMenu</term> - <listitem> - <synopsis>SystemMenu=false</synopsis> - <para> - Turns the Shutdown/Halt menu on/off. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>TitleBar</term> - <listitem> - <synopsis>TitleBar=true</synopsis> - <para> - Display the title bar in the greeter. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Use24Clock</term> - <listitem> - <synopsis>Use24Clock=false</synopsis> - <para> - Force the use of 24 hour clock even if the locale would default - to a 12 hour clock. In some locales that normally use 24 hour - format (like cs_CZ) this setting has no effect. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Welcome</term> - <listitem> - <synopsis>Welcome=Welcome to %n</synopsis> - <para> - Controls which text to display next to the logo image in the - greeter. The following control chars are supported: - </para> - - <para> - %% — the `%' character - </para> - - <para> - %d — display's hostname - </para> - - <para> - %h — Fully qualified hostname - </para> - - <para> - %m — machine (processor type) - </para> - - <para> - %n — Nodename (i.e. hostname without .domain) - </para> - - <para> - %r — release (OS version) - </para> - - <para> - %s — sysname (i.e. OS) - </para> - - </listitem> - </varlistentry> - - <varlistentry> - <term>XineramaScreen</term> - <listitem> - <synopsis>XineramaScreen=0</synopsis> - <para> - If the Xinerama extension is active the login window - will be centered on this physical screen (use 0 for - the first screen, 1 for the second..). - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundColor</term> - <listitem> - <synopsis>BackgroundColor=#007777</synopsis> - <para> - If the BackgroundType is 2, use this color in the background - of the greeter. Also use it as the back of transparent images - set on the background and if the BackgroundRemoteOnlyColor - is set and this is a remote display. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundImage</term> - <listitem> - <synopsis>BackgroundImage=somefile.png</synopsis> - <para> - If the BackgroundType is 1, then display this file as the - bacground in the greeter. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundProgram</term> - <listitem> - <synopsis>BackgroundProgram=/usr/bin/xeyes</synopsis> - <para> - If set this program will be run in the background while - the login window is being displayed. Note that not all - programs will run this way, since gdm does not usually have - a home directory. You could set up home directory for the - gdm user if you wish to run applications which require it. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundRemoteOnlyColor</term> - <listitem> - <synopsis>BackgroundRemoteOnlyColor=true</synopsis> - <para> - On remote displays only set the color background. This is - to make network load lighter. The BackgroundProgram is also - not run. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundScaleToFit</term> - <listitem> - <synopsis>BackgroundScaleToFit=true</synopsis> - <para> - Scale background image to fit the screen. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundType</term> - <listitem> - <synopsis>BackgroundType=2</synopsis> - <para> - The type of background to set. 0 is none, 1 is image and 2 - is color. - </para> - </listitem> - </varlistentry> - - - <varlistentry> - <term>SetPosition</term> - <listitem> - <synopsis>SetPosition=true</synopsis> - <para> - If true the position of the login window is determined - by PositionX/PositionY. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>PositionX</term> - <listitem> - <synopsis>PositionX=200</synopsis> - <para> - The horizontal position of the login window. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>PositionY</term> - <listitem> - <synopsis>PositionY=100</synopsis> - <para> - The vertical position of the login window. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ShowGnomeChooserSession</term> - <listitem> - <synopsis>ShowGnomeChooserSession=true</synopsis> - <para> - Should the greeter show the Gnome Chooser session, when - a session named 'Gnome' session is also present - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ShowGnomeFailsafeSession</term> - <listitem> - <synopsis>ShowGnomeFailsafeSession=true</synopsis> - <para> - Should the greeter show the Gnome Failsafe session - in the sessions list. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ShowXtermFailsafeSession</term> - <listitem> - <synopsis>ShowXtermFailsafeSession=true</synopsis> - <para> - Should the greeter show the Xterm Failsafe session - in the sessions list. - </para> - </listitem> - </varlistentry> - - </variablelist> - - </sect2> - - <sect2> - - <title>XDCMP Chooser Options</title> - - <variablelist> - <title>[chooser]</title> - - <varlistentry> - <term>Broadcast</term> - <listitem> - <synopsis>Broadcast=true</synopsis> - <para> - If true, the chooser will broadcast a query to the local - network and collect responses. This way the chooser will - always show all available managers on the network. If you - need to add some hosts not local to this network, or if you - don't want to use Broadcast, you can list them in the Hosts - key. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>DefaultHostImage</term> - <listitem> - <synopsis>DefaultHostImage=share/pixmaps/nohost.png</synopsis> - <para> - File name for the default host icon. This image will be - displayed if no icon is specified for a given host. The - file must be in an Imlib supported format and it must be - readable for the GDM user. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>HostImageDir</term> - <listitem> - <synopsis>HostImageDir=share/hosts</synopsis> - <para> - Repository for host icon files. The sysadmin can place - icons for remote hosts here and they will appear in - <filename>gdmchooser</filename>. - </para> - - <para> - The file name must match the fully qualified name (FQDN) for - the host. The icons must be stored in Imlib supported formats - and they must be readable to the gdm user. - </para> - - </listitem> - </varlistentry> - - <varlistentry> - <term>Hosts</term> - <listitem> - <synopsis>Hosts=host1,host2</synopsis> - <para> - The hosts which should be listed in the chooser. The chooser - will only list them if they respond. This is done in addition - to broadcast (if Broadcast is set), so you need not list - hosts on the local network. This is useful if your - networking setup doesn't allow all hosts to be reachable - by a broadcast packet. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ScanTime</term> - <listitem> - <synopsis>ScanTime=3</synopsis> - <para> - Specifies how many seconds the chooser should wait for - replies to its BROADCAST_QUERY. - </para> - </listitem> - </varlistentry> - </variablelist> - - </sect2> - - <sect2> - - <title>X Server definitions</title> - - <para> - To set up X servers, you need to provide gdm with - information about the installed X servers. You can - have as many different definitions as you wish, each - identified with a unique name. The name - <filename>Standard</filename> - is required. If you do not specify this server, gdm - will assume default values for a 'Standard' server - and the path given by <filename>daemon/StandardXServer</filename>. - <filename>Standard</filename> is used as the default, - in situations when no other server has been defined. - </para> - - <para> - Servers are defined by sections named <filename>server-</filename> - followed by the identifier of this server. This should be a - simple ascii string with no spaces. If you use the GUI - configurator, it will use random words for these. These will - not be user visible, they are just needed to uniquel identify the - server. - </para> - - <variablelist> - <title>[server-Standard]</title> - - <varlistentry> - <term>name</term> - <listitem> - <synopsis>name=Standard server</synopsis> - <para> - The name that will be displayed to the user. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>command</term> - <listitem> - <synopsis>command=/usr/bin/X11/X</synopsis> - <para> - The command to execute, with full path to the binary - of the X server, and any extra arguments needed. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>flexible</term> - <listitem> - <synopsis>flexible=true</synopsis> - <para> - Indicates if this server is available as a choice when a - user wishes to run a flexible server. - </para> - </listitem> - </varlistentry> - - </variablelist> - - </sect2> - - <sect2> - - <title>Local X Server Configuration</title> - - <variablelist> - <title>[servers]</title> - - <varlistentry> - <term>0</term> - <listitem> - <synopsis>0=Standard</synopsis> - <para> - Control section for local X servers. Each line indicates - the local display number and the command that needs to - be run to start the X server(s). - </para> - - <para> - The command can either be a path to an X executable, or - a name of one of the server definitions. This can be - followed by some arguments that should be passed to the - X server when executed. - </para> - - <para> - The gdm daemon doesn't enforce the numbers to be in - order or for them to be "packed". However when you use - the GUI configurator, the servers will always start from - 0 and go up by 1. That is, leaving no holes. - </para> - - <para> - GDM will splice "<filename>-auth - <ServAuthDir>/:n.Xauth :n</filename>", where n is - the display number. Inside the command line before all - other arguments before running the server. - </para> - - <para> - On some systems it is necessary for gdm to know on which - virtual consoles to run the X server. In this case, - (if running XFree86) add "vt7" to the command line for example - to run on virtual console 7. - </para> - </listitem> - </varlistentry> - - </variablelist> - - </sect2> - - </sect1> - - </chapter> - -</book> - -<!-- Keep this comment at the end of the file -Local variables: -mode: sgml -sgml-omittag:t -sgml-shorttag:t -sgml-minimize-attributes:nil -sgml-always-quote-attributes:t -sgml-indent-step:2 -sgml-indent-data:t -sgml-parent-document:nil -sgml-exposed-tags:nil -sgml-local-catalogs:nil -sgml-local-ecat-files:nil -End: ---> diff --git a/docs/C/gdm.xml b/docs/C/gdm.xml index 22dcab2c..fb345273 100644 --- a/docs/C/gdm.xml +++ b/docs/C/gdm.xml @@ -1,12 +1,13 @@ <?xml version="1.0"?> -<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" +<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [ -<!ENTITY version "1.4.0"> -<!ENTITY date "4/20/2001"> + <!ENTITY legal SYSTEM "legal.xml"> + <!ENTITY version "2.4.1.98"> + <!ENTITY date "7/19/2003"> ]> -<book id="index"> - <bookinfo> +<article id="index" lang="en"> + <articleinfo> <title>Gnome Display Manager Reference Manual</title> <authorgroup> <author> @@ -21,6 +22,12 @@ <address><email>jirka@5z.com</email></address> </affiliation> </author> + <author> + <firstname>Brian</firstname><surname>Cameron</surname> + <affiliation> + <address><email>Brian.Cameron@Sun.COM</email></address> + </affiliation> + </author> </authorgroup> <copyright> <year>1998, 1999</year> <holder>Martin K. Petersen</holder> @@ -28,34 +35,21 @@ <copyright> <year>2001</year> <holder>George Lebl</holder> </copyright> + <copyright> + <year>2003</year> <holder>Red Hat, Inc.</holder> + </copyright> + <copyright> + <year>2003</year> <holder>Sun Microsystems, Inc.</holder> + </copyright> + + &legal; - <!-- Use this legal notice for online documents which depend on --> - <!-- core GNOME packages. --> - <legalnotice id="legalnotice"> - <para> - Permission is granted to copy, distribute and/or modify this document - under the terms of the <ulink type="help" - url="gnome-help:fdl"><citetitle>GNU Free Documentation - License</citetitle></ulink>, Version 1.1 or any later version - published by the Free Software Foundation with no Invariant Sections, - no Front-Cover Texts, and no Back-Cover Texts. A copy of the license - can be found <ulink type="help" url="gnome-help:fdl">here</ulink>. - </para> - <para> - Many of the names used by companies to distinguish their products and - services are claimed as trademarks. Where those names appear in any - GNOME documentation, and those trademarks are made aware to the members - of the GNOME Documentation Project, the names have been printed in caps - or initial caps. - </para> - </legalnotice> - - <releaseinfo> + <releaseinfo> This manual describes version &version; of the GNOME Display Manager. It was last updated on &date;. - </releaseinfo> + </releaseinfo> - </bookinfo> + </articleinfo> <toc></toc> @@ -72,7 +66,16 @@ </para> <para> - Greeter - The graphical login window (<filename>gdmlogin</filename>). + Greeter - The graphical login window (<filename>gdmlogin</filename> or + <filename>gdmgreeter</filename>). + </para> + + <para> + Standard Greeter - The standard login window (<filename>gdmlogin</filename>). + </para> + + <para> + Graphical Greeter - The themable login window (<filename>gdmgreeter</filename>). </para> <para> @@ -81,7 +84,7 @@ </para> <para> - Configurator - The configuration program (<filename>gdmconfig</filename>). + Configurator - The configuration program (<filename>gdmsetup</filename>). </para> <para> @@ -93,10 +96,10 @@ </preface> - <chapter id="intro"> + <sect1 id="overview"> <title>Overview</title> - <sect1> + <sect2 id="introduction"> <title> Introduction </title> @@ -106,9 +109,9 @@ competitors (X3DM, KDM, WDM) GDM was written from scratch and does not contain any original XDM / X Consortium code. </para> - </sect1> + </sect2> - <sect1 id="daemonov"> + <sect2 id="daemonov"> <title>The GDM Daemon</title> <para> @@ -119,9 +122,11 @@ <para> Upon startup the <filename>gdm</filename> daemon parses its config file <filename>gdm.conf</filename>. For each of the local displays <filename>gdm</filename> - forks an Xserver and a slave process. The main <filename>gdm</filename> process - will then listen to XDMCP requests from remote displays and - monitor the local display sessions. + forks an Xserver and a slave process. The main <filename>gdm</filename> process + will then listen to XDMCP requests, if so configured, from remote displays and + monitor the local display sessions. The main daemon process will also allow + starting of on new local Xservers on demand using the <filename>gdmflexiserver</filename> + command. </para> <para> @@ -129,7 +134,12 @@ <filename>gdmlogin</filename>, the graphical login program. <filename>gdmlogin</filename> runs as a dedicated user and communicates asynchronously with the slave process - through a pipe. + through a pipe. Alternatively <filename>gdmgreeter</filename> command + can be used which is the same as <filename>gdmlogin</filename> but + allows greater themability. <filename>gdmgreeter</filename> + is refered to as the Graphical Greeter, while + <filename>gdmlogin</filename> is refered to as the Standard + Greeter. </para> <para> @@ -179,9 +189,55 @@ reasons. Looking up icons in homedirs, scaling and rendering face icons can take quite a long time. YMMV. </para> - </sect1> - <sect1> + <para> + GDM also has a unix domain socket which can be used to control + certain aspects of behaviour, or to query information about running + servers or logged in users. This is the <filename>/tmp/.gdm_socket</filename> + and the protocol is described in the sources in the + <filename>daemon/gdm.h</filename> header file. The + <filename>gdmflexiserver</filename> command uses this for example to + launch on demand X servers for the user. + </para> + + </sect2> + + <sect2 id="displaytypes"> + <title>Different Display Types</title> + + <para> + GDM allows 3 different display types. First local static X servers. These + are always run, and when they die or are killed, they are restarted. GDM + can run as many of these as needed. GDM can also manage servers on which it + does not manage a login itself, thus allowing GDM to be used when building + X terminals. + </para> + + <para> + Next GDM supports flexible or on demand servers. These are run by + requesting one using the socket protocol. There is a command, + <filename>gdmflexiserver</filename>, which can do this for the user. + For standard X servers the user must be logged in from a console, on + one of the servers that GDM has run. This command can however also + launch nested <filename>Xnest</filename> servers which can be started + even from non-console logins. This is generally done by running + <filename>gdmflexiserver -n</filename>. These servers + are not restarted when the user session ends. + <filename>gdmflexiserver</filename> normally also locks the users + screen screen before running a new server with xscreensaver. + </para> + + <para> + Last display type is the XDMCP remote displays that are described + in the next section. Remote hosts can connect to GDM and present + the login screen if this is enabled. Some things may be different + for these sessions, such as the Actions menu which allows you to + shut down, reboot, or configure GDM will not be shown. + </para> + + </sect2> + + <sect2 id="xdmcp"> <title> XDMCP </title> @@ -201,7 +257,12 @@ GDM can also be configured to honor INDIRECT queries and present a host chooser to the remote display. GDM will remember the user's choice and forward subsequent requests to - the chosen manager. + the chosen manager. GDM also supports an extension to the + protocol which will make it forget the redirection once + the user's connection succeeds. This extension is only + supported if both daemons are GDM. It is transparent and + will be ignored by XDM or other daemons that implement + XDMCP. </para> <para> @@ -222,7 +283,9 @@ still adviced that you block UDP port 177 on your firewall unless you really need it. GDM guards against DoS attacks, but the X protocol is still inherently insecure and should only be - used in controlled environments. + used in controlled environments. Also each remote connection + takes up lots of resources, so it is much easier to to DoS + an XDMCP server. </para> <para> @@ -233,129 +296,180 @@ NFS mounted directory, are prone to eavesdropping too. </para> - </sect1> + </sect2> - <sect1> - <title>The Greeter</title> + <sect2 id="stdgreeter"> + <title>The Standard Greeter</title> <para> - The greeter is the graphical user interface that is presented - to the user. The greeter contains a menu at the top, an + The Standard Greeter is the default graphical user interface that + is presented to the user. The greeter contains a menu at the top, an optional face browser, an optional logo and a text entry widget. </para> - <sect2> - <title> - Text entry - </title> + <para> + The text entry field is used for entering logins, passwords, + passphrases etc. <filename>gdmlogin</filename> is controlled by the + underlying daemon and is basically stateless. The daemon + controls the greeter through a simple protocol where it can + ask the greeter for a text string with echo turned on or + off. Similarly, the daemon can change the label above the + text entry widget to correspond to the value the + authentication system wants the user to enter. + </para> - <para> - The text entry field is used for entering logins, passwords, - passphrases etc. <filename>gdmlogin</filename> is controlled by the - underlying daemon and is basically stateless. The daemon - controls the greeter through a simple protocol where it can - ask the greeter for a text string with echo turned on or - off. Similarly, the daemon can change the label above the - text entry widget to correspond to the value the - authentication system wants the user to enter. - </para> + <para> + The menu bar in the top of the greeter enables the user to + select the requested session type/desktop environment, + select an appropriate locale/language and optionally + shutdown/reboot the machine. The greeter window can also be + iconified to make room for other applications on the login + screen. + </para> - </sect2> + <para> + The greeter provides a face browser containing icons for all + the users on a system. The icons can be installed globally + by the sysadmin or in the users' home directories. If installed + globally they should be in the <filename>share/faces/</filename> + directory (though this can be configured with the + <filename>GlobalFaceDir</filename> + configuration option) and the filename should be the name of + the user, optionally with a <filename>.png</filename> appended. + </para> - <sect2> - <title> - The Menu - </title> + <para> + The users can place their icons in a file called <filename>~/.face</filename>, + and they can use the program <filename>gdmphotosetup</filename> to + graphically configure this. + </para> + + <para> + Face icons placed in the global face directory + must be readable to the gdm user. However, the daemon, proxies + user pictures to the greeter and thus those don't have be be + readable by the gdm user, but root. + </para> - <para> - The menu bar in the top of the greeter enables the user to - select the requested session type/desktop environment, - select an appropriate locale/language and optionally - shutdown/reboot the machine. The greeter window can also be - iconified to make room for other applications on the login - screen. - </para> + <para> + Please note that loading and scaling face icons located in + user home directories can be a very time consuming task. + Especially on large systems or systems running NIS. The + browser feature is only intended for systems with relatively + few users. + </para> - </sect2> + <para> + To filter out unwanted user names in the browser, an exclude + option is implemented. The greeter will automatically ignore + usernames listed in the <filename>Exclude</filename> statement in the + config file. + </para> - <sect2> - <title> - The face browser - </title> + <para> + When the browser is turned on, valid usernames on the + machine are inherently exposed to a potential intruder. If + your system is connected directly to the Internet, this + might be a bad idea. + </para> - <para> - The greeter provides a face browser containing icons for all - the users on a system. The icons can be installed globally - by the sysadmin or in the users' home directories. - </para> - - <para> - Face icons placed in the global face directory - must be readable to the gdm user. However, the daemon, proxies - user pictures to the greeter and thus those don't have be be - readable by the gdm user, but root. - </para> + <para> + The greeter can optionally display a logo in the login + window. The image must be in a format readable to the gdk-pixbuf + library (GIF, JPG, PNG, TIFF, XPM and possibly others), and + it must be readable to the gdm user. See the <filename> + Logo</filename> option in the reference section below for detauls. + </para> - <para> - Please note that loading and scaling face icons located in - user home directories can be a very time consuming task. - Especially on large systems or systems running NIS. The - browser feature is only intended for systems with relatively - few users. - </para> + </sect2> - <para> - To filter out unwanted user names in the browser, an exclude - option is implemented. The greeter will automatically ignore - usernames listed in the <filename>Exclude</filename> statement in the - config file. - </para> + <sect2 id="graphgreeter"> + <title>The Graphical Greeter</title> - <para> - When the browser is turned on, valid usernames on the - machine are inherently exposed to a potential intruder. If - your system is connected directly to the Internet, this - might be a bad idea. - </para> + <para> + The Graphical Greeter is a greeter interface that takes up the whole + screen and is very themable. Themes can be selected and new themes + can be installed by the Configuration program or by setting the + <filename>GraphicalTheme</filename> configuration key. + </para> - </sect2> + <para> + The look and feel of this greeter is really controlled by the theme and + so the user interface elements that are present may be different. The + only thing that must always be present is the text entry field as described + above in the Standard Greeter. + </para> - <sect2> - <title> - The Logo - </title> + <para> + You can always get a menu of available actions by pressing the F10 key. + This can be useful if the theme doesn't provide certain buttons when you + really wish to do some action. + </para> - <para> - The greeter can optionally display a logo in the login - window. The image must be in a format readable to the Imlib - library (GIF, JPG, PNG, TIFF, XPM and possibly others), and - it must be readable to the gdm user. See the <filename> - Logo</filename> option in the reference section below for detauls. - </para> + </sect2> - </sect2> + <sect2 id="logging"> + <title>Logging</title> + + <para> + GDM itself will use syslog to log errors or status. It can also + log debugging information, but this is not generally useful unless + something is very wrong, and this must be enabled in the configuration + file. + </para> + + <para> + Output from the various X servers is stored in the GDM log directory, + which is configurable, but is usually <filename>var/log/gdm/</filename>. + The output from the session can be found in a file called + <filename><display>.log</filename>. Four older files are + also stored with <filename>.1</filename> through + <filename>.4</filename> appended. These will be rotated as new + sessions on that display are started. You can use these logs + to view what the X server said when it started up. + </para> + + <para> + The output from the user session is redirected to <filename>~/.xsession-errors</filename> + before even the <filename>PreSession</filename> script is started. So + it is not really necessary to redirect this again in the session setup + script. As is usually done. If the user session lasted less then + 10 seconds, GDM assumes that the session crashed and allows the user to + view this file in a dialog before returning to the login screen. + Also if the session being started is one of the failsafe session, this + file is not created. This way the user can view the session errors from + the last session and correct the problem this way. + </para> - </sect1> + </sect2> - </chapter> + </sect1> - <chapter id="Configuration"> - <title>The Configuration Directory</title> + <sect1 id="configuration"> + <title>Configuration</title> <para> - This chapter will cover the structure of the configuration - directory and the format of the configuration file. However you - can use the <filename>gdmconfig</filename> binary to configure - GDM from a graphical environment. The terms from this chapter - could however still come in handy. If you want to run the - configurator from the GNOME menu, it should be installed under - the <filename>System</filename> submenu. + This section will cover the configuration of GDM + and the format of the configuration file. However you + can use the <filename>gdmsetup</filename> binary to configure + GDM from a graphical environment. The configuration program + does not however let you configure every aspect of GDM however, + so if the setup program does not cover your needs + you may find information in this section. + </para> + + <para> + The configuration files, and especially the <filename>gdm.conf</filename> + file, contain lots of useful comments, so also read these when + changing your setup. </para> <para> The configuration files for GDM are located in the - <filename>etc/gdm/</filename> directory. + <filename>etc/gdm/</filename> directory. And some which + can be shared among other display managers are + located in the <filename>etc/dm/</filename> directory. </para> <para> @@ -364,37 +478,66 @@ <screen> Init/ + PostLogin/ PostSession/ PreSession/ - Sessions/ gdm.conf + factory-gdm.conf + locale.alias + Xsession + XKeepsCrashing </screen> <para> <filename>gdm.conf</filename> is the main GDM configuration file. The - options will be described later in this chapter. + options will be described later in this section. + <filename>factory-gdm.conf</filename> is the configuration file as shipped + with the daemon. This can be useful if you wish to revert to the default + configuration. + </para> + + <para> + <filename>locale.alias</filename> is a file which looks much like the + system locale alias but in fact it is not the same. These are the languages + that are available on your system. All the languages are still tested to + see if they actually exist before presenting them to the user. + </para> + + <para> + <filename>Xsession</filename> is a script which sets up a user session + and then executes the users choice of session. + </para> + + <para> + <filename>XKeepsCrashing</filename> is a script which gets run when the + X server keeps crashing and we cannot recover. The shipped default script + will work with most Linux distributions and can run the X configuration + program provided the person on the console knows the root password. </para> <para> <filename>gdm.conf</filename> is configuration file for both <filename> - gdm</filename>, <filename>gdmlogin</filename>, and <filename>gdmchooser</filename> since a - lot of parameters overlap. + gdm</filename>, <filename>gdmgreeter</filename>, <filename>gdmlogin</filename>, + and <filename>gdmchooser</filename> since a lot of parameters overlap. </para> - <para> + <para> The remaining configuration is done by dropping scripts in the - subdirectories of the <filename>etc/gdm</filename> folder. This + subdirectories of the <filename>etc/gdm</filename> folder or + dropping <filename>.desktop</filename> style files in + <filename>etc/dm/Sessions</filename>. This approach makes it easy for package management systems to install window managers and different session types without requiring the sysadmin to edit files. </para> - <sect1> + <sect2 id="scriptdirs"> <title>The Script Directories</title> <para> In this section we will explain the <filename>Init</filename>, - <filename>PreRoot</filename> and <filename>PostRoot</filename> directories as + <filename>PostLogin</filename>, + <filename>PreSession</filename> and <filename>PostSession</filename> directories as they are very similar. </para> @@ -403,7 +546,13 @@ to run the script called <filename>Init/<displayname></filename>. I.e. <filename>Init/:0</filename> for the first local display. If this file is not found, GDM - will attempt to to run <filename>Init/Default</filename>. The + will attempt to to run + <filename>Init/<hostname></filename>. I.e. <filename>Init/somehost</filename>. + If this still is not found, GDM will try + <filename>Init/XDMCP</filename> for all XDMCP logins or + <filename>Init/Flexi</filename> for all on demand flexible + servers. If none of the above were found, GDM will run + <filename>Init/Default</filename>. The script will be run as root and GDM blocks until it terminates. Use the <filename>Init/*</filename> script for programs that are supposed to run alongside with the GDM login @@ -414,48 +563,75 @@ <para> It is up to the sysadmin to decide whether clients started by the Init script should be killed before starting the user - session. This is controlled with the KillInitClients option in - <filename>gdm.conf</filename>. + session. This is controlled with the <filename>KillInitClients</filename> + option in <filename>gdm.conf</filename>. + </para> + + <para> + When the user has been successfully authenticated GDM tries the + scripts in the <filename>PostLogin</filename> directory in the + same manner as for the <filename>Init</filename> directory. + This is done before any session setup is done, and so this + would be the script where you might setup the home directory + if you need to (though you should use the + <filename>pam_mount</filename> module if you can for this). + You have the $USER and $DISPLAY environment variables set for this script, + and again it is run as root. </para> <para> - When the user has been successfully authenticated, GDM tries - to run the PreSession script. Similar to the Init-scripts, - <filename>PreSession/<displayname></filename> will be - executed, if this file doesn't exist, GDM will attempt to run - <filename>PreSession/Default</filename>. The script will be - run as root and GDM blocks until it terminates. Use this + After the user session has been setup from the GDM side of + things, GDM will run the scripts in the <filename>PreSession</filename> + directory, again in the same manner as the <filename>Init</filename> + directory. Use this script for local session management or accounting stuff. The $USER environment variable contains the login of the - authenticated user. The script should return 0 on success. Any + authenticated user and $DISPLAY is set to the current display. + The script should return 0 on success. Any other value will cause GDM to terminate the current login process. + Also $X_SERVERS environmental variable is set and this points + to a fake generated x servers file for use with the + sessreg accounting program. + </para> + + <para> + After this the base <filename>Xsession</filename> script is + run with the selected session executable as the first argument. + This is run as the user, and really this is the user session. + The available session executables are taken from the + <filename>Exec=</filename> line in the + <filename>.desktop</filename> files in the + <filename>etc/dm/Sessions</filename> directory. The user + either picks from these sessions or GDM will look inside + the file <filename>~/.dmrc</filename> for the stored + preferrence. </para> <para> - Then the session script is run. Session scripts are located in - the <filename>etc/gdm/Session</filename> directory. Which one - GDM runs, depends on the session the user chose in the - Sessions-menu in the greeter. If no session is selected and - the user has no last session stored in his - <filename>~/.gnome/gdm</filename> file, the system will choose - or first script found or -- if - <filename>Sessions/Default</filename> exists -- this will be - run. For instance you can create a symlink from - <filename>Gnome</filename> to <filename>Default</filename> to - make Gnome the default desktop environment. + This script should really load the users profile and generally + do all the voodoo that is needed to launch a session. Since + many systems reset the language selections done by GDM, GDM + will also set the GDM_LANG variable to the selected language. + You can use this to reset the language environmental + variables after you run the users profile. If the user + elected to use the system language, then GDM_LANG is not run. </para> <para> - When the user terminates his session, the PostSession script - will be run. Operation is similar to Init and PreSession. That - is, GDM will attempt to execute the script - <filename>PostSession/<displayname></filename> and if - that doesn't exist <filename>PostSession/Default</filename> - will be run. Again the script will be run with root + When the user terminates his session, the <filename>PostSession</filename> script + will be run. Again operation is similar to <filename>Init</filename>, + <filename>PostLogin</filename> and + <filename>PreSession</filename>. + Again the script will be run with root priviledges, the slave daemon will block and the $USER environment variable will contain the name of the user who - just logged out. + just logged out and $DISPLAY will be set to the display + the user used, however note that the X server for this display + may already be dead and so you shouldn't try to access it. + Also $X_SERVERS environmental variable is set and this points + to a fake generated x servers file for use with the + sessreg accounting program. </para> <para> @@ -465,15 +641,23 @@ script execution. </para> + <para> + Except for the <filename>Xsession</filename> script all of these + scripts will also have the environment of + <filename>RUNNING_UNDER_GDM=yes</filename> set, so that you could + perhaps use similar scripts for different display managers. + </para> + <para> - Neither of the Init, PreSession or PostSession scripts are + Neither of the <filename>Init</filename>, <filename>PostLogin</filename>, + <filename>PreSession</filename> or <filename>PostSession</filename> scripts are necessary and can be left out. At least one session script is required for proper operation. </para> - </sect1> + </sect2> - <sect1> + <sect2 id="configfile"> <title>The Configuration File - <filename>gdm.conf</filename></title> <para> @@ -484,17 +668,20 @@ <para> The configuration file is divided into sections each containing variables that define the behaviour for a specific - part of the GDM suite. + part of the GDM suite. The file is fairly well commented + as well. </para> <para> - <filename>gdm.conf</filename> follows the standard GNOME configuration + <filename>gdm.conf</filename> follows the standard <filename>.ini</filename> + style configuration file syntax. Keywords in brackets define sections, strings before an equal sign (=) are variables and the data after - equal sign represents their value. + equal sign represents their value. Empty lines or lines + starting with the hash mark (#) are ignored. </para> - <sect2> + <sect3 id="daemonsection"> <title>Daemon Configuration</title> <variablelist> @@ -536,7 +723,7 @@ first bootup. No password will be asked. This is useful for single user workstations where local console security is not an issue. Also could be useful for public terminals, - although there see TimedLogin. + although there see <filename>TimedLogin</filename>. </para> </listitem> </varlistentry> @@ -554,11 +741,24 @@ </para> </listitem> </varlistentry> + + <varlistentry> + <term>BaseXsession</term> + <listitem> + <synopsis>BaseXsession=etc/gdm/Xsession</synopsis> + <para> + This is the base X session file. When a user logs in, this script + will be run with the selected session as the first argument. The + selected session will be the <filename>Exec=</filename> from + the <filename>.desktop</filename> file of the session. + </para> + </listitem> + </varlistentry> <varlistentry> <term>Chooser</term> <listitem> - <synopsis>Chooser=bin/gdmchooser --disable-sound --disable-crash-dialog</synopsis> + <synopsis>Chooser=bin/gdmchooser</synopsis> <para> Full path and name of the chooser executable followed by optional arguments. </para> @@ -568,11 +768,11 @@ <varlistentry> <term>Configurator</term> <listitem> - <synopsis>Configurator=bin/gdmconfig --disable-sound --disable-crash-dialog</synopsis> + <synopsis>Configurator=bin/gdmsetup --disable-sound --disable-crash-dialog</synopsis> <para> The pathname to the configurator binary. If the greeter - ConfigAvailable option is set to true then run this binary - when somebody chooses Configuration from the system menu. + <filename>ConfigAvailable</filename> option is set to true then run this binary + when somebody chooses Configuration from the Actions menu. Of course GDM will first ask for root password however. And it will never allow this to happen from a remote display. </para> @@ -588,6 +788,19 @@ </para> </listitem> </varlistentry> + + <varlistentry> + <term>DefaultSession</term> + <listitem> + <synopsis>DefaultSession=gnome.desktop</synopsis> + <para> + The session that is used by default if the user does not have + a saved preference and has picked 'Last' from the list of + sessions. + </para> + </listitem> + </varlistentry> + <varlistentry> <term>DisplayInitDir</term> @@ -601,6 +814,19 @@ </varlistentry> <varlistentry> + <term>DoubleLoginWarning</term> + <listitem> + <synopsis>DoubleLoginWarning=true</synopsis> + <para> + If true, GDM will warn the user if they are already logged in on + another virtual terminal. On systems where GDM supports checking + the X virtual terminals, GDM will let the user switch to the + previous login virtual terminal instead of logging in. + </para> + </listitem> + </varlistentry> + + <varlistentry> <term>FailsafeXServer</term> <listitem> <synopsis>FailsafeXServer=</synopsis> @@ -614,36 +840,38 @@ </varlistentry> <varlistentry> - <term>FlexibleXServers</term> + <term>FirstVT</term> <listitem> - <synopsis>FlexibleXServers=5</synopsis> + <synopsis>FirstVT=7</synopsis> <para> - The maximum number of allowed flexible servers. These are - servers that can be run using the /tmp/.gdm_socket socket - connection. This is used for both full servers and for - Xnest servers. + On systems where GDM supports automatic VT (virtual terminal) + allocation, this is the first vt to try. Usually standard text + logins are run on the lower vts. See also <filename>VTAllocation</filename>. </para> </listitem> </varlistentry> <varlistentry> - <term>GnomeDefaultSession</term> + <term>FlexibleXServers</term> <listitem> - <synopsis>GnomeDefaultSession=share/gnome/default.session</synopsis> + <synopsis>FlexibleXServers=5</synopsis> <para> - The filename which GDM should read if there is no per user - GNOME session file, and the user has requested the Gnome - Chooser session. + The maximum number of allowed flexible servers. These are + servers that can be run using the /tmp/.gdm_socket socket + connection. This is used for both full servers and for + Xnest servers. </para> </listitem> </varlistentry> - + <varlistentry> <term>Greeter</term> <listitem> - <synopsis>Greeter=bin/gdmlogin --disable-sound --disable-crash-dialog</synopsis> + <synopsis>Greeter=bin/gdmlogin</synopsis> <para> Full path and name of the greeter executable followed by optional arguments. + This is the greeter used for all servers except for the XDMCP remote servers. + See also <filename>RemoteGreeter</filename> </para> </listitem> </varlistentry> @@ -678,7 +906,9 @@ <synopsis>HaltCommand=/sbin/shutdown -h now</synopsis> <para> Full path and arguments to command to be executed when - user selects Halt from the System menu. + user selects Shut Down from the Actions menu. This can be a ';' + separated list of commands to try. + If missing, the shutdown command is not available. </para> </listitem> </varlistentry> @@ -716,6 +946,18 @@ </para> </listitem> </varlistentry> + + <varlistentry> + <term>PostLoginScriptDir</term> + <listitem> + <synopsis>PostLoginScriptDir=etc/gdm/PostLogin</synopsis> + <para> + Directory containing the scripts run right after the + user logs in, but before any session setup is done. + See the ``Script Directories'' section for more info. + </para> + </listitem> + </varlistentry> <varlistentry> <term>PostSessionScriptDir</term> @@ -747,7 +989,23 @@ <synopsis>RebootCommand=/sbin/shutdown -r now</synopsis> <para> Full path and optional arguments to the program to be - executed when user selects Reboot from the System menu. + executed when user selects Reboot from the Actions menu. + This can be a ';' separated list of commands to try. + If missing, the reboot command is not available. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>RemoteGreeter</term> + <listitem> + <synopsis>RemoteGreeter=bin/gdmlogin</synopsis> + <para> + Full path and name of the greeter executable followed by optional arguments. This + is used for all remote XDMCP sessions. It is useful to have the less + graphically demanding greeter here if you use the Graphical Greeter for your main + greeter. + See also the <filename>Greeter</filename> key. </para> </listitem> </varlistentry> @@ -781,12 +1039,12 @@ </varlistentry> <varlistentry> - <term>SessionDir</term> + <term>SessionDesktopDir</term> <listitem> - <synopsis>SessionDir=etc/gdm/Sessions</synopsis> + <synopsis>SessionDesktopDir=etc/dm/Sessions</synopsis> <para> - Directory containing the scripts for all session types - available on the system. + Directory containing the .desktop files which are the available + sessions on the system. </para> </listitem> </varlistentry> @@ -811,7 +1069,7 @@ <synopsis>SuspendCommand=</synopsis> <para> Full path and arguments to command to be executed when - user selects Suspend from the System menu. If empty + user selects Suspend from the Actions menu. If empty there is no such menu item. </para> </listitem> @@ -904,6 +1162,20 @@ </varlistentry> <varlistentry> + <term>VTAllocation</term> + <listitem> + <synopsis>VTAllocation=true</synopsis> + <para> + On systems where GDM supports automatic VT (virtual terminal) + allocation (currently Linux only), you can have GDM automatically append the vt argument + to the X server executable. This way races that come up from each X + server managing it's own vt allocation can be avoided. + See also <filename>FirstVT</filename>. + </para> + </listitem> + </varlistentry> + + <varlistentry> <term>XKeepsCrashing</term> <listitem> <synopsis>XKeepsCrashing=etc/gdm/XKeepsCrashing</synopsis> @@ -937,9 +1209,9 @@ </varlistentry> </variablelist> - </sect2> + </sect3> - <sect2> + <sect3 id="securitysection"> <title>Security Options</title> <variablelist> @@ -996,6 +1268,20 @@ </para> </listitem> </varlistentry> + + <varlistentry> + <term>DisallowTCP</term> + <listitem> + <synopsis>DisallowTCP=true</synopsis> + <para> + If true, then always append "-nolisten tcp" to the command line + of local X servers, thus disallowing TCP connection. This is + useful if you do not care for allowing remote connections, since + the X protocol could really be potentially a security hazard to + leave open, even though no known security problems exist. + </para> + </listitem> + </varlistentry> <varlistentry> <term>RelaxPermissions</term> @@ -1074,11 +1360,9 @@ </para> <para> - In addition to the size check both - <filename>gdm</filename> and - <filename>gdmlogin</filename> are extremely picky - about accessing files in user directories. Neither - will follow symlinks and they can optionally refuse to + In addition to the size check GDM is extremely picky + about accessing files in user directories. It will not + follow symlinks and can optionally refuse to read files and directories writable by other than the owner. See the RelaxPermissions option for more info. </para> @@ -1086,9 +1370,9 @@ </varlistentry> </variablelist> - </sect2> + </sect3> - <sect2> + <sect3 id="xdmcpsection"> <title>XDCMP Support</title> <variablelist> @@ -1271,6 +1555,16 @@ a combination of the xdm PingInterval and PingTimeout, but in seconds. </para> + + <para> + Note that GDM in the past used to have a <filename>PingInterval</filename> + configuration key which was also in minutes. For most purposes + you'd want this setting to be lower then one minute however since + in most cases where XDMCP would be used (such as terminal labs), + a lag of more then 15 or so seconds would really mean that the + terminal was turned off or rebooted and you would want to end + the session. + </para> </listitem> </varlistentry> @@ -1294,9 +1588,9 @@ </varlistentry> </variablelist> - </sect2> + </sect3> - <sect2> + <sect3 id="commonguioptions"> <title>Common GUI Configuration Options</title> <variablelist> @@ -1339,22 +1633,113 @@ </varlistentry> </variablelist> - </sect2> + </sect3> - <sect2> + <sect3 id="greetersection"> <title>Greeter Configuration</title> <variablelist> <title>[greeter]</title> - + + <varlistentry> + <term>BackgroundColor</term> + <listitem> + <synopsis>BackgroundColor=#007777</synopsis> + <para> + If the BackgroundType is 2, use this color in the background + of the greeter. Also use it as the back of transparent images + set on the background and if the BackgroundRemoteOnlyColor + is set and this is a remote display. + This only affects the Standard Greeter. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>BackgroundImage</term> + <listitem> + <synopsis>BackgroundImage=somefile.png</synopsis> + <para> + If the BackgroundType is 1, then display this file as the + bacground in the greeter. + This only affects the Standard Greeter. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>BackgroundProgram</term> + <listitem> + <synopsis>BackgroundProgram=/usr/bin/xeyes</synopsis> + <para> + If set this program will be run in the background while + the login window is being displayed. Note that not all + programs will run this way, since gdm does not usually have + a home directory. You could set up home directory for the + gdm user if you wish to run applications which require it. + This only affects the Standard Greeter. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>BackgroundRemoteOnlyColor</term> + <listitem> + <synopsis>BackgroundRemoteOnlyColor=true</synopsis> + <para> + On remote displays only set the color background. This is + to make network load lighter. The BackgroundProgram is also + not run. This only affects the Standard Greeter. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>BackgroundScaleToFit</term> + <listitem> + <synopsis>BackgroundScaleToFit=true</synopsis> + <para> + Scale background image to fit the screen. + This only affects the Standard Greeter. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>BackgroundType</term> + <listitem> + <synopsis>BackgroundType=2</synopsis> + <para> + The type of background to set. 0 is none, 1 is image and 2 + is color. + This only affects the Standard Greeter. + </para> + </listitem> + </varlistentry> + <varlistentry> <term>Browser</term> <listitem> <synopsis>Browser=true</synopsis> <para> - Set to true to enable the face browser. See the ``Greeter'' - section for more information on the face browser. + Set to true to enable the face browser. See the ``The Standard Greeter'' + section for more information on the face browser. This option only + works for the Standard Greeter. For the Graphical Greeter, + the face browser is enabled by choosing a theme which includes a + face browser + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>ChooserButton</term> + <listitem> + <synopsis>ChooserButton=true</synopsis> + <para> + If true, add a chooser button to the Actions menu that will + restart the current server with a chooser. XDMCP does not need + to be enabled on the local machine for this to work. </para> </listitem> </varlistentry> @@ -1366,7 +1751,7 @@ <para> Allow the configurator to be run from the greeter. Note that the user will need to type in the root password before the - configurator is run however. See the Configurator option + configurator is run however. See the <filename>Configurator</filename> option in the daemon section. </para> </listitem> @@ -1379,43 +1764,20 @@ <para> Default icon file for users without a personal picture in <filename>~/gnome/photo</filename>. The image must be - in an Imlib supported format and the file must be + in an gdk-pixbuf supported format and the file must be readable for the gdm user. </para> </listitem> </varlistentry> <varlistentry> - <term>DefaultLocale</term> - <listitem> - <synopsis>DefaultLocale=english</synopsis> - <para> - This language is used for the session unless nothing is - specified in <filename>~user/.gnome/gdm</filename> and - the user didn't select a language in the Locale menu in - the greeter. - </para> - </listitem> - </varlistentry> - - <varlistentry> <term>Exclude</term> <listitem> <synopsis>Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,...</synopsis> <para> Comma-separated list of usernames to exclude from the face browser. The excluded users will still be able to - log in. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Font</term> - <listitem> - <synopsis>Font=-adobe-helvetica-bold-r-normal-*-*-180-*-*-*-*-*-*</synopsis> - <para> - Font to use for the welcome message in the greeter. + log in. See also <filename>MinimalUID</filename>. </para> </listitem> </varlistentry> @@ -1437,7 +1799,7 @@ </para> <para> - The face images must be stored in Imlib supported formats and + The face images must be stored in gdk-pixbuf supported formats and they must be readable for the GDM user. </para> @@ -1447,6 +1809,29 @@ </para> </listitem> </varlistentry> + + <varlistentry> + <term>GraphicalTheme</term> + <listitem> + <synopsis>GraphicalTheme=circles</synopsis> + <para> + The graphical theme that the Graphical Greeter should use. + it should refer to a directory in the theme directory + set by <filename>GraphicalThemeDir</filename>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>GraphicalThemeDir</term> + <listitem> + <synopsis>GraphicalThemeDir=share/gdm/themes/</synopsis> + <para> + The directory where themes for the Graphical Greeter are + installed. + </para> + </listitem> + </varlistentry> <varlistentry> <term>Icon</term> @@ -1454,10 +1839,11 @@ <synopsis>Icon=share/pixmaps/gdm.xpm</synopsis> <para> Icon to use for <filename>gdmlogin</filename> when it's - in the iconified state. The image must be in an Imlib + in the iconified state. The image must be in an gdk-pixbuf supported format and it must be readable for the GDM user. If no file is specified the iconify feature is disabled. + This only affects the Standard Greeter. </para> </listitem> </varlistentry> @@ -1467,11 +1853,23 @@ <listitem> <synopsis>LocaleFile=etc/gdm/locale.alias</synopsis> <para> - File in GNU locale format with entries for all supported - languages on the system. + File in format similar to the GNU locale format with entries + for all supported languages on the system. The format is + described above or in a comment inside that file. </para> </listitem> </varlistentry> + + <varlistentry> + <term>LockPosition</term> + <listitem> + <synopsis>LockPosition=true</synopsis> + <para> + If true the position of the login window of the Standard Greeter + cannot be changed even if the title bar is turned on. + </para> + </listitem> + </varlistentry> <varlistentry> <term>Logo</term> @@ -1479,250 +1877,231 @@ <synopsis>Logo=share/pixmaps/gnome-logo-large.png</synopsis> <para> Image file to display in the logo box. The file must be - in an Imlib supported format and it must be readable by + in an gdk-pixbuf supported format and it must be readable by the GDM user. If no file is specified the logo feature is disabled. + This only affects the Standard Greeter. </para> </listitem> </varlistentry> - + <varlistentry> - <term>Quiver</term> + <term>MinimalUID</term> <listitem> - <synopsis>Quiver=true</synopsis> + <synopsis>MinimalUID=100</synopsis> <para> - Controls whether <filename>gdmlogin</filename> should - shake the display when an incorrect username/password is - entered. + The minimal UID that gdm should consider a user. All + users with a lower UID will be excluded from the face browser. + See also <filename>Exclude</filename>. </para> </listitem> </varlistentry> - + <varlistentry> - <term>SystemMenu</term> + <term>PositionX</term> <listitem> - <synopsis>SystemMenu=false</synopsis> + <synopsis>PositionX=200</synopsis> <para> - Turns the Shutdown/Halt menu on/off. + The horizontal position of the login window of the Standard Greeter. </para> </listitem> - </varlistentry> + </varlistentry> <varlistentry> - <term>TitleBar</term> + <term>PositionY</term> <listitem> - <synopsis>TitleBar=true</synopsis> + <synopsis>PositionY=100</synopsis> <para> - Display the title bar in the greeter. + The vertical position of the login window of the Standard Greeter. </para> </listitem> - </varlistentry> - + </varlistentry> + <varlistentry> - <term>Use24Clock</term> + <term>Quiver</term> <listitem> - <synopsis>Use24Clock=false</synopsis> + <synopsis>Quiver=true</synopsis> <para> - Force the use of 24 hour clock even if the locale would default - to a 12 hour clock. In some locales that normally use 24 hour - format (like cs_CZ) this setting has no effect. + Controls whether <filename>gdmlogin</filename> should + shake the display when an incorrect username/password is + entered. + This only affects the Standard Greeter. </para> </listitem> </varlistentry> - + <varlistentry> - <term>Welcome</term> + <term>RemoteWelcome</term> <listitem> - <synopsis>Welcome=Welcome to %n</synopsis> + <synopsis>RemoteWelcome=Welcome to %n</synopsis> <para> Controls which text to display next to the logo image in the - greeter. The following control chars are supported: - </para> - - <para> - %% — the `%' character - </para> - - <para> - %d — display's hostname - </para> - - <para> - %h — Fully qualified hostname - </para> - - <para> - %m — machine (processor type) - </para> - - <para> - %n — Nodename (i.e. hostname without .domain) + greeter for remote XDMCP sessions. The same expansion is + done here as in the <filename>Welcome</filename> string. </para> - - <para> - %r — release (OS version) - </para> - - <para> - %s — sysname (i.e. OS) - </para> - </listitem> </varlistentry> <varlistentry> - <term>XineramaScreen</term> + <term>RunBackgroundProgramAlways</term> <listitem> - <synopsis>XineramaScreen=0</synopsis> + <synopsis>RunBackgroundProgramAlways=false</synopsis> <para> - If the Xinerama extension is active the login window - will be centered on this physical screen (use 0 for - the first screen, 1 for the second..). + If this is true then the background program is run always, otherwise + it is only run when the <filename>BackgroundType</filename> is 0 (None) + This only affects the Standard Greeter. </para> </listitem> </varlistentry> <varlistentry> - <term>BackgroundColor</term> + <term>SetPosition</term> <listitem> - <synopsis>BackgroundColor=#007777</synopsis> + <synopsis>SetPosition=true</synopsis> <para> - If the BackgroundType is 2, use this color in the background - of the greeter. Also use it as the back of transparent images - set on the background and if the BackgroundRemoteOnlyColor - is set and this is a remote display. + If true the position of the login window of the Standard Greeter + is determined by PositionX/PositionY. </para> </listitem> </varlistentry> <varlistentry> - <term>BackgroundImage</term> + <term>ShowGnomeFailsafeSession</term> <listitem> - <synopsis>BackgroundImage=somefile.png</synopsis> + <synopsis>ShowGnomeFailsafeSession=true</synopsis> <para> - If the BackgroundType is 1, then display this file as the - bacground in the greeter. + Should the greeter show the Gnome Failsafe session + in the sessions list. </para> </listitem> </varlistentry> <varlistentry> - <term>BackgroundProgram</term> + <term>ShowXtermFailsafeSession</term> <listitem> - <synopsis>BackgroundProgram=/usr/bin/xeyes</synopsis> + <synopsis>ShowXtermFailsafeSession=true</synopsis> <para> - If set this program will be run in the background while - the login window is being displayed. Note that not all - programs will run this way, since gdm does not usually have - a home directory. You could set up home directory for the - gdm user if you wish to run applications which require it. + Should the greeter show the Xterm Failsafe session + in the sessions list. </para> </listitem> </varlistentry> + <varlistentry> - <term>BackgroundRemoteOnlyColor</term> + <term>SystemMenu</term> <listitem> - <synopsis>BackgroundRemoteOnlyColor=true</synopsis> + <synopsis>SystemMenu=false</synopsis> <para> - On remote displays only set the color background. This is - to make network load lighter. The BackgroundProgram is also - not run. + Turns the Shutdown/Reboot/Configure menu on/off. If this is off + none of the functions will be available even if a theme for + a graphical greeter mistakenly shows them. Normally this is + called the Actions menu. </para> </listitem> - </varlistentry> + </varlistentry> <varlistentry> - <term>BackgroundScaleToFit</term> + <term>TitleBar</term> <listitem> - <synopsis>BackgroundScaleToFit=true</synopsis> + <synopsis>TitleBar=true</synopsis> <para> - Scale background image to fit the screen. + Display the title bar in the greeter. + This only affects the Standard Greeter. </para> </listitem> - </varlistentry> + </varlistentry> <varlistentry> - <term>BackgroundType</term> + <term>Use24Clock</term> <listitem> - <synopsis>BackgroundType=2</synopsis> + <synopsis>Use24Clock=false</synopsis> <para> - The type of background to set. 0 is none, 1 is image and 2 - is color. + Force the use of 24 hour clock even if the locale would default + to a 12 hour clock. In some locales that normally use 24 hour + format (like cs_CZ) this setting has no effect. </para> </listitem> - </varlistentry> - + </varlistentry> <varlistentry> - <term>SetPosition</term> + <term>UseCirclesInEntry</term> <listitem> - <synopsis>SetPosition=true</synopsis> + <synopsis>UseCirclesInEntry=false</synopsis> <para> - If true the position of the login window is determined - by PositionX/PositionY. + Use circles instead of asteriscs in the password entry. </para> </listitem> - </varlistentry> - + </varlistentry> + <varlistentry> - <term>PositionX</term> + <term>Welcome</term> <listitem> - <synopsis>PositionX=200</synopsis> + <synopsis>Welcome=Welcome</synopsis> <para> - The horizontal position of the login window. + Controls which text to display next to the logo image in the + greeter. The following control chars are supported: + </para> + + <para> + %% — the `%' character + </para> + + <para> + %d — display's hostname + </para> + + <para> + %h — Fully qualified hostname </para> - </listitem> - </varlistentry> - <varlistentry> - <term>PositionY</term> - <listitem> - <synopsis>PositionY=100</synopsis> <para> - The vertical position of the login window. + %m — machine (processor type) </para> - </listitem> - </varlistentry> - <varlistentry> - <term>ShowGnomeChooserSession</term> - <listitem> - <synopsis>ShowGnomeChooserSession=true</synopsis> <para> - Should the greeter show the Gnome Chooser session, when - a session named 'Gnome' session is also present + %n — Nodename (i.e. hostname without .domain) + </para> + + <para> + %r — release (OS version) + </para> + + <para> + %s — sysname (i.e. OS) </para> - </listitem> - </varlistentry> - <varlistentry> - <term>ShowGnomeFailsafeSession</term> - <listitem> - <synopsis>ShowGnomeFailsafeSession=true</synopsis> <para> - Should the greeter show the Gnome Failsafe session - in the sessions list. + This string is only used for local logins. For remote XDMCP + logins we use <filename>RemoteWelcome</filename>. + </para> + + <para> + In the Graphical Greeter the location of this text depends on + the theme. Unless the theme uses the stock welcome string + this string will not be displayed at all. </para> + </listitem> - </varlistentry> + </varlistentry> <varlistentry> - <term>ShowXtermFailsafeSession</term> + <term>XineramaScreen</term> <listitem> - <synopsis>ShowXtermFailsafeSession=true</synopsis> + <synopsis>XineramaScreen=0</synopsis> <para> - Should the greeter show the Xterm Failsafe session - in the sessions list. + If the Xinerama extension is active the login window + will be centered on this physical screen (use 0 for + the first screen, 1 for the second..). </para> </listitem> </varlistentry> </variablelist> - </sect2> + </sect3> - <sect2> + <sect3 id="choosersection"> <title>XDCMP Chooser Options</title> @@ -1730,6 +2109,18 @@ <title>[chooser]</title> <varlistentry> + <term>AllowAdd</term> + <listitem> + <synopsis>AllowAdd=true</synopsis> + <para> + If true, allow the user to add arbitrary hosts to the + chooser. This way the user could connect to any host + that responds to XDMCP queries from the chooser. + </para> + </listitem> + </varlistentry> + + <varlistentry> <term>Broadcast</term> <listitem> <synopsis>Broadcast=true</synopsis> @@ -1751,7 +2142,7 @@ <para> File name for the default host icon. This image will be displayed if no icon is specified for a given host. The - file must be in an Imlib supported format and it must be + file must be in an gdk-pixbuf supported format and it must be readable for the GDM user. </para> </listitem> @@ -1769,7 +2160,7 @@ <para> The file name must match the fully qualified name (FQDN) for - the host. The icons must be stored in Imlib supported formats + the host. The icons must be stored in gdk-pixbuf supported formats and they must be readable to the gdm user. </para> @@ -1794,18 +2185,20 @@ <varlistentry> <term>ScanTime</term> <listitem> - <synopsis>ScanTime=3</synopsis> + <synopsis>ScanTime=4</synopsis> <para> Specifies how many seconds the chooser should wait for - replies to its BROADCAST_QUERY. + replies to its BROADCAST_QUERY. Really this is only the time + in which we expect a reply. We will still add hosts to the list + even if they reply after this time. </para> </listitem> </varlistentry> </variablelist> - </sect2> + </sect3> - <sect2> + <sect3 id="serverdefs"> <title>X Server definitions</title> @@ -1861,16 +2254,46 @@ <synopsis>flexible=true</synopsis> <para> Indicates if this server is available as a choice when a - user wishes to run a flexible server. + user wishes to run a flexible, on demand server. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>handled</term> + <listitem> + <synopsis>handled=true</synopsis> + <para> + Indicates that GDM should run the login window on this server + and allow a user to log in. If set to false, then GDM will just + run this server and wait for it to terminate. This can be useful + to run an X terminal using GDM. When this is done you should + normally also add <filename>-terminate</filename> to the command + line of the server to make the server terminate after each session. + otherwise the control of the slave will never come back to GDM + and for example soft restarts won't work, since GDM assumes there + is a login in progress for the entire time this server is + active. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>chooser</term> + <listitem> + <synopsis>chooser=false</synopsis> + <para> + Indicates that GDM should instead of a login window run a chooser on + this window and allow the user to choose which server to log into. </para> </listitem> </varlistentry> </variablelist> - </sect2> + </sect3> - <sect2> + <sect3 id="localservers"> <title>Local X Server Configuration</title> @@ -1912,54 +2335,928 @@ On some systems it is necessary for gdm to know on which virtual consoles to run the X server. In this case, (if running XFree86) add "vt7" to the command line for example - to run on virtual console 7. + to run on virtual console 7. However on Linux this is normally + done automatically if <filename>VTAllocation</filename> key + is set. + </para> + + <para> + Normally you do not need to add a <filename>-nolisten tcp</filename> + flag as this is added automatically for local servers when + the <filename>DisallowTCP</filename> option is set. </para> </listitem> </varlistentry> </variablelist> - </sect2> + </sect3> - </sect1> + </sect2> - <!-- ============= Application License ============================= --> + <sect2 id="userconfig"> + <title>Per User Configuration</title> - <sect1 id="license"> - <title>License</title> <para> - This program is free software; you can redistribute it and/or - modify it under the terms of the <ulink type="help" url="gnome-help:gpl"> - <citetitle>GNU General Public License</citetitle></ulink> as - published by the Free Software Foundation; - either version 2 of the License, or (at your option) any later - version. + There are some per user configuration settings that control how GDM behaves. + Firstly there is the <filename>~/.dmrc</filename> file. In theory this + file should be shared between GDM and KDM, so users only have to configure + things once. This is a standard <filename>.ini</filename> style configuration + file. It has one section called <filename>[Desktop]</filename> and can have + two keys, <filename>Session</filename>, which is the basename of the session + <filename>.desktop</filename> file that the user wishes to normally use + and a <filename>Language</filename> key that is the language that the user + wishes to use. If either of these keys is missing, the system default is + used. The file would normally look as follows: </para> + + <screen> + [Desktop] + Session=gnome.desktop + Language=cs_CZ.UTF-8 + </screen> + <para> - This program is distributed in the hope that it will be useful, but - WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - <citetitle>GNU General Public License</citetitle> for more details. + The user can also configure a face image for the face browser. This is + done by copying an image into a file called <filename>~/.face</filename>. + This should be a standard image that GTK+ can read, such as PNG. </para> + <para> - A copy of the <citetitle>GNU General Public License</citetitle> is - included as an appendix to the <citetitle>GNOME Users - Guide</citetitle>. You may also obtain a copy of the - <citetitle>GNU General Public License</citetitle> from the Free - Software Foundation by visiting <ulink type="http" - url="http://www.fsf.org">their Web site</ulink> or by writing to - <address> - Free Software Foundation, Inc. - <street>59 Temple Place</street> - Suite 330 - <city>Boston</city>, <state>MA</state> <postcode>02111-1307</postcode> - <country>USA</country> - </address> + Face images can also be placed in the global face directory, which is + normally <filename>share/faces/</filename> + (though this can be configured with the <filename>GlobalFaceDir</filename> + configuration option) and the filename should be the name of + the user, optionally with a <filename>.png</filename> appended. </para> - </sect1> + </sect2> - </chapter> + </sect1> + + <sect1 id="controlling"> + <title>Controlling GDM</title> + + <para> + You can control GDM behaviour during runtime in several different ways. You can + either run certain commands, or you can talk to GDM using either a unix socket + protocol, or a FIFO protocol. + </para> + + <sect2 id="commands"> + <title>Commands</title> + + <para> + To stop GDM, you can either send the TERM signal to the main daemon or run + the <filename>gdm-stop</filename> command which is in the <filename>sbin/</filename> + directory. To restart GDM, you can either send the HUP signal to the main daemon or run + the <filename>gdm-restart</filename> command which is also in the <filename>sbin/</filename> + directory. + To restart GDM but only after all the users have logged out, you can either send + the USR1 signal to the main daemon or run + the <filename>gdm-safe-restart</filename> command which is in the <filename>sbin/</filename> + directory as well. + </para> + + <para> + The <filename>gdmflexiserver</filename> command can be used to start new flexible (on demand) + servers. Run <filename>gdmflexiserver --help</filename> to get a listing of possible + options. This command will also lock the current screen with xscreensaver so that + the user can safely walk away from the machine and let someone else log in. XFree86 will + automatically switch back to the same virtual terminal (if your operating system supports it), + after the new session has ended, so this should work quite transparently to the users. + </para> + + </sect2> + + <sect2 id="socketprot"> + <title>Socket Protocol</title> + + <para> + GDM provides a unix domain socket for communication at <filename>/tmp/.gdm_socket</filename>. + Using this you can check if GDM is running, the version of the daemon, the current + servers that are running and who is logged in on them, and if GDM supports it on your + operating system, also the virtual terminals of all the console logins. You can also request + new flexible servers to be run with this protocol, but this is best done with the + <filename>gdmflexiserver</filename> command. + </para> + + <para> + Full and up to date documentation of the commands and their use is contained in the + GDM source tree in the file <filename>daemon/gdm.h</filename>. Look for the + defines starting with <filename>GDM_SUP_</filename>. + </para> + + </sect2> + + <sect2 id="fifoprot"> + <title>The FIFO protocol</title> + + <para> + GDM also provides a FIFO called <filename>.gdmfifo</filename> in the + <filename>ServAuthDir</filename> directory + (usually <filename>var/gdm/.gdmfifo</filename>). You must be root to use this protocol, + and it is mostly used for internal GDM chatter. It is a very simple protocol where + you just echo a command on a single line to this file. It can be used to tell + GDM things such as restart, suspend the machine, or restart all X servers next + time it has a chance (which would be useful from an X configuration program). + </para> + + <para> + Full and up to date documentation of the commands and their use is contained in the + GDM source tree in the file <filename>daemon/gdm.h</filename>. Look for the + defines starting with <filename>GDM_SOP_</filename>. The commands which require the + pid of the slave as an argument are the ones that are really used for internal + communication of the slave with the master and should not be used. + </para> + + </sect2> + </sect1> + + <sect1 id="binaries"> + <title>GDM and Related Commands</title> + + <para> + The GDM package provides quite a few different commands. + </para> + + <sect2 id="mainbinaries"> + <title>Main GDM Commands</title> + + <para> + First is the <filename>gdm</filename> command which is really just a script + which runs the <filename>gdm-binary</filename>. If you really need to set + some environment before launching GDM, you can do it in this file. + </para> + + <para> + Next are the two greeters, <filename>gdmlogin</filename> which is the + Standard Greeter, and <filename>gdmgreeter</filename> which is the + Graphical Greeter. There is also the <filename>gdmchooser</filename> + which is the XDMCP chooser application. These should all be run + only from GDM and not by itself, although <filename>gdmchooser</filename> + could theoretically be run as a standalone application which prints + the chosen host on the standard output. + </para> + + <para> + There is also the setup program which is the <filename>gdmsetup</filename> + command. Normally on systems that support the PAM userhelper, this + is setup such that when you run <filename>gdmsetup</filename> as + an ordinary user, it will first ask you for your root password. + </para> + + <para> + There is also the user picture setup program, <filename>gdmphotosetup</filename>. + This is run by users to setup their face browser picture. + </para> + + <para> + There are also the commands <filename>gdm-stop</filename>, <filename>gdm-restart</filename> + and <filename>gdm-safe-restart</filename> which stop, restart, or restart the + GDM daemon after all users have logged out, respectivelly. These are + installed in the <filename>sbin/</filename> directory. + </para> + + <para> + Finally there is the <filename>gdmflexiserver</filename> command which runs + flexible (on demand) X servers. + </para> + + </sect2> + + <sect2 id="extrabins"> + <title>Extra GDM Commands</title> + + <para> + There are some extra commands provided as well. First is the <filename>gdmXnestchooser</filename> + command. This command can run Xnest with all the right options and automatically getting + the correct display number and setting up access, and runs the server as an indirect query + to the local host by default. This way you get an XDMCP chooser provided by your machine. + You can also supply as an argument the hostname whose chooser should be displayed, so + <filename>gdmXnestchooser somehost</filename> will run the XDMCP chooser from host + <filename>somehost</filename> inside an Xnest. You can make this command do a direct query + instead by passing the <filename>-d</filename> option as well. + </para> + + <para> + Also useful is the <filename>gdmXnest</filename> command which is just for more + easily running Xnest on your machine. It will print out the display setting on standard + output that you can use to connect to this server. This is useful mostly for developers + who perhaps wish to test their apps running on a completely separate server. + </para> + + <para> + For Graphical Greeter theme developers, there is the <filename>gdmthemetester</filename> + command which can run the Graphical Greeter in a simulated debug environment for any + selected theme. Run the command with no options to get help. + </para> + + </sect2> + </sect1> + + <!-- ============= Theme manual ============================= --> + + <sect1 id="thememanual"> + <title>Graphical Greeter Themes</title> + + <para> + This section describes the creation of themes for the Graphical + Greeter. For examples including screenshots, see the standard installed + themes and the themes from + <ulink type="http" url="http://art.gnome.org/theme_list.php?category=gdm_greeter"> + the theme website</ulink>. + </para> + + <sect2 id="themeover"> + <title>Theme Overview</title> + + <para> + GDM Themes can be created by creating an XML file that follows the + specification in gui/greeter/greeter.dtd. Theme files are stored + in the directory <filename>share/gdm/themes/<theme_name></filename>. + Usually this would be under /usr/share. The theme directory should contain a + file called <filename>GdmGreeterTheme.desktop</filename> which has similar format to other + .desktop files and looks like: + </para> + + <screen> + [GdmGreeterTheme] + Encoding=UTF-8 + Greeter=circles.xml + Name=Circles + Description=Theme with blue circles + Author=Bond, James Bond + Copyright=(c) 2002 Bond, James Bond + Screenshot=screenshot.png + </screen> + + <para> + The Name, Description, Author and Copyright fields can be translated just + like the other <filename>.desktop</filename>files. All the files that are mentioned should + be in the theme directory itself. The Screenshot field points to a file + which should be a 200x150 screenshot of the theme in action (it is ok + not to have one, but it makes it nicer for user). The Greeter field points + to an XML file that contains the description of the theme. The description + will be given later. + </para> + + <para> + Once you have theme ready and installed you can test it with the installed + <filename>gdmthemetester</filename> script. This script assumes that you also have installed + the Xnest X server. It takes two arguments, first the environment that + should be used. This is one of console, console-timed, flexi, remote-flexi, + xdmcp. Where console is a standard console login, console-timed is a + console login with a timed login going on, flexi is for any local + flexible server, remote-flexi is for flexi server that is not local (such + as an Xnest flexiserver run from a remote display) and xdmcp is for remote + xdmcp connections. The second argument is the theme name. So for example + to test how things look in the xdmcp mode with the circles theme you would + run: + </para> + + <screen> + gdmthemetester xdmcp circles + </screen> + + <para> + Be sure to test all the environments with your theme, and make sure to test + how the caps lock warning looks by pressing capslock. This is also a good + way to take screenshots, just take a screenshot of the Xnest window. This + can be done in GNOME by focusing the Xnest window and pressing + Alt-PrintScreen. + </para> + + <para> + Once you have all this done, then make a tarball that contains the directory + name (so that you could just untar it in the <filename>/usr/share/gdm/themes</filename> directory). + And this is the tarball you distribute and people can install from the + graphical setup program. You can do this with the commands: + </para> + + <screen> + cd /usr/share/gdm/themes + tar czvf <theme_name>.tar.gz <theme_name>/ + </screen> + + </sect2> + + <sect2 id="descofthemeformat"> + <title>Detailed Description of Theme XML format</title> + + <sect3 id="boxnodes"> + <title>Box Nodes</title> + + <para> + Box nodes are container nodes for item nodes. Box nodes are + specified as follows: + </para> + + <screen> + <box orientation="alignment" min-width="int" xpadding="int" + ypadding="int" spacing="int"> + </screen> + + <para> + The alignment value can be either "horizontal" or "vertical". + </para> + </sect3> + + <sect3 id="itemnodes"> + <title>Item Nodes</title> + + <para> + A GDM Theme is created by specifying a hierarchy of item and box + nodes. Item nodes can have the following value for "type": + </para> + + <variablelist> + <varlistentry> + <term>entry</term> + <listitem> + <para> + Text entry field. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>list</term> + <listitem> + <para> + A list widget. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>label</term> + <listitem> + <para> + A text label. Must have a "text" node to specify the text. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>pixmap</term> + <listitem> + <para> + An pixmap image in a format that gdk-pixbuf supports like + PNG, JPEG, Tiff, etc...) + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>rect</term> + <listitem> + <para> + Rectangle. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>svg</term> + <listitem> + <para> + Scaled Vector Graphic image. + </para> + </listitem> + </varlistentry> + </variablelist> + + <para> + For example: + </para> + + <screen> + <item type="label"> + </screen> + + <para> + Items can specify ID values which gives them a specific look + and feel or formatting. Furthermore you can customize the login + process by adding custom widgets with custom id's for some items + (currently only the list item) + </para> + + <para> + Entry items can have id values as follows: + </para> + + <variablelist> + <varlistentry> + <term>user-pw-entry</term> + <listitem> + <para> + Entry field for userid and password entry. This is + the field used for responses for the PAM/GDM questions + (Username, Password, etc..). + </para> + </listitem> + </varlistentry> + </variablelist> + + + <para> + List items can have id values as follows: + </para> + + <variablelist> + <varlistentry> + <term>userlist</term> + <listitem> + <para> + A user browser list, so that users can pick + their username by clicking on this instead + of typing. + </para> + </listitem> + </varlistentry> + </variablelist> + + <para> + Furthermore, you can have an arbitrary id (I'd recommend starting + the id with 'custom' not to conflict with future additions to this + spec) and ask extra information of the user. See the section + 'Custom Widgetry' + </para> + + <para> + Label items can have id values as follows: + </para> + + <variablelist> + <varlistentry> + <term>clock</term> + <listitem> + <para> + Label the displays the date and time. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>pam-prompt</term> + <listitem> + <para> + Label the displays PAM prompt. This is the prompt that + PAM uses to ask for username, password, etc... + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>pam-error</term> + <listitem> + <para> + Label the displays PAM/GDM error messages. Such as when + user can't log in. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>pam-message</term> + <listitem> + <para> + Label the displays PAM message. These are messages that + PAM/GDM gives about state of the account, help about the + prompts and other information. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>timed-label</term> + <listitem> + <para> + Label that displays timed login information. + </para> + </listitem> + </varlistentry> + </variablelist> + + <para> + Rectangles can have id values as follows: + </para> + + <variablelist> + <varlistentry> + <term>caps-lock-warning</term> + <listitem> + <para> + Displays an icon that shows if the + CAPS LOCK key is depressed. This rectangle + will be hidden/shown appropriately + </para> + </listitem> + </varlistentry> + </variablelist> + + <para> + If an item is of type rect, the item can be a button. Buttons + must also include a "button" value as follows: + </para> + + <screen> + <item type="rect" id="disconnect_button" button="true">. + </screen> + + <para> + Possible values for button ids are as follows: + </para> + + <variablelist> + <varlistentry> + <term>chooser_button</term> + <listitem> + <para> + Runs the XDMCP chooser. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>config_button</term> + <listitem> + <para> + Runs the GDM Setup program. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>disconnect_button</term> + <listitem> + <para> + Disconnect from remote session. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>language_button</term> + <listitem> + <para> + Displays the language selection dialog. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>halt_button</term> + <listitem> + <para> + Halt (shuts down) the system. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>reboot_button</term> + <listitem> + <para> + Reboot the system. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>session_button</term> + <listitem> + <para> + List and select from available sessions. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>suspend_button</term> + <listitem> + <para> + Suspend the system. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>system_button</term> + <listitem> + <para> + Perform halt/reboot/suspend/etc. options + (if allowed by gdm configuration). Also + allows user to run configurator if user + enters root password (again if allowed + by gdm configuration). This is usually + now labeled Actions, and refered to as + the Actions menu. + </para> + </listitem> + </varlistentry> + + </variablelist> + </sect3> + + <sect3 id="positionnodes"> + <title>Position Node</title> + + <para> + Each item can specify its position and size via the "pos" node. + For example: + </para> + + <screen> + <pos x="0" y="4" width="100%" height="100%"/> + </screen> + </sect3> + + <sect3 id="shownodes"> + <title>Show Node</title> + + <para> + Some items may only display in certain modes, like when doing a + remote display. Multiple values can be specified and must be + separated with commas. The following values are possible: + </para> + + <para> + <filename>console</filename> - In console mode. + <para> + </para> + <filename>console-fixed</filename> - In console non-flexi mode. + <para> + </para> + <filename>console-flexi</filename> - In console & flexi mode. + <para> + </para> + <filename>flexi</filename> - In flexi mode. + <para> + </para> + <filename>remote</filename> - In remote mode. + <para> + </para> + <filename>remote-flexi</filename> - In remote & flexi mode. + </para> + + <para> + For example: + </para> + + <screen> + <show modes="flexi,remote"/> + </screen> + + <para> + You can also specify the "type" value to indicate that certain + items should only be displayed if the type is true. Valid values + include the following: + </para> + + <para> + <filename>chooser</filename>, if ChooserButton is set to "true" in <filename>gdm.conf</filename> file. + </para> + <para> + <filename>config</filename>, if ConfigAvailable is set to "true" in <filename>gdm.conf</filename> file. + </para> + <para> + <filename>halt</filename>, if HaltDaemon is specified in <filename>gdm.conf</filename> file. + </para> + <para> + <filename>reboot</filename>, if RebootCommand is specified in <filename>gdm.conf</filename> file. + </para> + <para> + <filename>suspend</filename>, if SuspendCommand is specified in <filename>gdm.conf</filename> file. + </para> + <para> + <filename>system</filename>, if SystemMenu is specified in <filename>gdm.conf</filename> file + </para> + <para> + <filename>timed</filename>, if TimedLoginEnabled is set to "true" in <filename>gdm.conf</filename> file. + </para> + + <para> + For example: + </para> + + <screen> + <show modes="console" type="system"/> + </screen> + + <para> + Note that if SystemMenu is off then all of halt, reboot, suspend, chooser + and config will not show, so this is a global toggle for them all. + See some of the standard themes for how the show modes are used. + </para> + </sect3> + + <sect3 id="noractprenodes"> + <title>Normal/Active/Prelight Nodes</title> + + <para> + Depending on the item type, it can specify its color, font, or + image via the following tags: + </para> + + <para> + <filename>normal</filename> - normal state. + <para> + </para> + <filename>active</filename> - when the item has active focus. + <para> + </para> + <filename>prelight</filename> - when the mouse is hovering over the item. + </para> + + <para> + When item is "rect" (alpha can be omitted and defaults to 0.0): + </para> + + <screen> + <normal color="#fffff" alpha="0.0"> + </screen> + + <para> + When item is "label": + </para> + + <screen> + <normal color="#ffffff" font="Sans 14"/> + </screen> + + <para> + When the item type is "pixmap" or "SVG", then the normal, active, + and prelight tags specify the images to use as follows: + </para> + + <screen> + <normal file="picture.png" tint="#dddddd"/> + </screen> + + <para> + Note that relative pathnames are assumed to be in the same + directory as the theme .xml file in share/gdm/themes/<theme_name>. + </para> + </sect3> + + <sect3 id="textnodes"> + <title>Text Node</title> + + <para> + Text tags are used by labels. They can be used to display + localized text as follows (if the "xml:lang" attribute is + omitted, the C locale is assumed): + </para> + + <screen> + <text xml:lang="fr">Option</text> + </screen> + + <para> + You can include pango markup in the text nodes for labels, however + you must encode it. So for example to have the label of + "foo<sup>bar</sup>", you must type: + </para> + + <screen> + <text">foo&lt;sup&gt;bar&lt;/sup&gt;</text> + </screen> + + </sect3> + + <sect3 id="stocklabels"> + <title>Stock</title> + + <para> + Certain common localized labels can be specified via the stock + tags. The "text" tag is ignored if the "stock" tag is used. You + should really use the stock labels rather then just putting all + the translations into the themes. This gives faster load times + and likely better translations. The following values are valid: + </para> + + <para> + <filename>caps-lock-warning</filename>, _("You've got capslock on!") + <para> + </para> + <filename>chooser</filename>, _("_XDMCP Chooser") + <para> + </para> + <filename>disconnect</filename>, _("D_isconnect") + <para> + </para> + <filename>language</filename>, _("_Language") + <para> + </para> + <filename>quit</filename>, _("_Quit") + <para> + </para> + <filename>session</filename>, _("_Session") + <para> + </para> + <filename>system</filename>, _("_Actions") (Formerly "S_ystem") + <para> + </para> + <filename>timed-label</filename>, _("User %s will login in %d seconds") + <para> + </para> + <filename>username-label</filename>, _("Username:") + <para> + </para> + <filename>welcome-label</filename>, _("Welcome to %h") + </para> + + <para> + For example: + </para> + + <screen> + <stock type="welcome-label"/> + </screen> + + </sect3> + + <sect3 id="customwidgetry"> + <title>Custom Widgetry</title> + + <para> + Currently there is one item which can be customizable and this is + the list item. If you need to ask the user extra things, such as + to pick from a list of places to log into, or set of custom login + sessions you can setup the list item and add listitem children that + describe the choices. Each listitem must have an id and a text child. + The choice will be recorded in the file + <filename><ServAuthDir>/<display>.GreeterInfo</filename> + as <filename><list id>=<listitem id></filename>. + </para> + + <para> + For example suppose we are on display :0, ServAuthDir is /var/gdm + and we have the following in the theme: + </para> + + <screen> + <item type="list" id="custom-config"> + <pos anchor="nw" x="1" y="1" height="200" width="100"/> + <listitem id="foo"> + <text>Foo</text> + </listitem> + <listitem id="bar"> + <text>Bar</text> + </listitem> + </item> + </screen> + + <para> + Then if the user chooses 'Foo' then <filename>/var/gdm/:0.GreeterInfo</filename> will + contain: + </para> + + <screen> + custom-config=foo + </screen> + + </sect3> + </sect2> + </sect1> + + + <!-- ============= Application License ============================= --> + + <sect1 id="license"> + <title>License</title> + <para> + This program is free software; you can redistribute it and/or + modify it under the terms of the <ulink type="help" url="gnome-help:gpl"> + <citetitle>GNU General Public License</citetitle></ulink> as + published by the Free Software Foundation; + either version 2 of the License, or (at your option) any later + version. + </para> + <para> + This program is distributed in the hope that it will be useful, but + WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + <citetitle>GNU General Public License</citetitle> for more details. + </para> + <para> + A copy of the <citetitle>GNU General Public License</citetitle> is + included as an appendix to the <citetitle>GNOME Users + Guide</citetitle>. You may also obtain a copy of the + <citetitle>GNU General Public License</citetitle> from the Free + Software Foundation by visiting <ulink type="http" + url="http://www.fsf.org">their Web site</ulink> or by writing to + <address> + Free Software Foundation, Inc. + <street>59 Temple Place</street> - Suite 330 + <city>Boston</city>, <state>MA</state> <postcode>02111-1307</postcode> + <country>USA</country> + </address> + </para> + </sect1> -</book> +</article> <!-- Keep this comment at the end of the file Local variables: diff --git a/docs/GdmGreeterThemeManual.txt b/docs/GdmGreeterThemeManual.txt index 2a97dcf3..6c18feb8 100644 --- a/docs/GdmGreeterThemeManual.txt +++ b/docs/GdmGreeterThemeManual.txt @@ -3,7 +3,7 @@ GDM Theme Manual By Brian Cameron <Brian.Cameron@Sun.COM> Updated by George Lebl <jirka@5z.com> -Last Updated: July 15, 2003 +Last Updated: July 18, 2003 ======================================== GDM Themes can be created by creating an XML file that follows the @@ -91,7 +91,9 @@ Item Nodes: <item type="label"> Items can specify ID values which gives them a specific look - and feel or formatting: + and feel or formatting. Furthermore you can customize the login + process by adding custom widgets with custom id's for some items + (currently only the list item) entry: @@ -109,6 +111,11 @@ Item Nodes: their username by clicking on this instead of typing. + Furthermore, you can have an arbitrary id (I'd recommend starting + the id with 'custom' not to conflict with future additions to this + spec) and ask extra information of the user. See the section + 'Custom Widgetry' + label: Label items can have id values as follows: @@ -252,6 +259,35 @@ Stock: <stock type="welcome-label"/> +Custom Widgetry: + + Currently there is one item which can be customizable and this is + the list item. If you need to ask the user extra things, such as + to pick from a list of places to log into, or set of custom login + sessions you can setup the list item and add listitem children that + describe the choices. Each listitem must have an id and a text child. + The choice will be recorded in the file + <ServAuthDir>/<display>.GreeterInfo as <list id>=<listitem id> + + For example suppose we are on display :0, ServAuthDir is /var/gdm + and we have the following in the theme: + + <item type="list" id="custom-config"> + <pos anchor="nw" x="1" y="1" height="200" width="100"/> + <listitem id="foo"> + <text>Foo</text> + </listitem> + <listitem id="bar"> + <text>Bar</text> + </listitem> + </item> + + Then if the user chooses 'Foo' then /var/gdm/:0.GreeterInfo will + contain: + + custom-config=foo + + Examples of themes with photos can be found here: http://art.gnome.org/theme_list.php?category=gdm_greeter diff --git a/docs/Makefile.am b/docs/Makefile.am index 342212b4..40fc4251 100644 --- a/docs/Makefile.am +++ b/docs/Makefile.am @@ -1 +1,2 @@ +SUBDIRS = . C EXTRA_DIST = GdmGreeterThemeManual.txt diff --git a/docs/gdm-manual.txt b/docs/gdm-manual.txt deleted file mode 100644 index 5f72af94..00000000 --- a/docs/gdm-manual.txt +++ /dev/null @@ -1,375 +0,0 @@ - - -***** THIS DOCUMENT IS NO LONGER MAINTAINED ***** -***** Please read C/gdm.sgml ***** - - -The Gnome Display Manager - -1. Theory of operation - -gdm is a replacement for xdm, the X Display Manager. Unlike its -competitors (x3dm, kdm, wdm) gdm was written from scratch and does not -contain any original xdm code. - -gdm was written with simplicity and security in mind. The overall -design concept is this: - -When gdm starts it parses the config file gdm.conf. For each of the -local displays gdm forks a slave process. The main gdm process will -listen to XDMCP requests from remote displays and monitor the local -display sessions. - -The gdm slave process starts an Xserver according to information read -from the config file. gdm sets up proper X authentication and starts -up the greeter window requesting the user for login and password. - -The gdm master and slave processes are deliberately kept small and -they are believed to be secure. The program providing the user -interface is significantly more complex and is linked to several -unaudited libraries. Therefore it runs as a dedicated gdm user and -communicates with gdm through a pipe. - - -2. Overview of the config directory. - -The configuration files for gdm are located in the <prefix>/etc/gdm/ -directory. - -This is a listing of the config directory contents: - - Init/ - PostSession/ - PreSession/ - Sessions/ - gdm.conf - -gdm.conf is the main gdm configuration file. The options will be -described later in this document. - -The remaining configuration is done by dropping scripts in the -subdirectories of the gdm folder. This approach makes it easy for -package management systems to install window managers and different -session types without requiring the sysadmin/user to edit files. - -In this section we will explain the Init, PreRoot and PostRoot -directories as they are very similar. - -When the X server has been successfully started, gdm will try to run -the script called Init/<displayname>. I.e. Init/:0 for the first local -display. If this file is not found, gdm will attempt to to run -Init/Default. The script will be run as root and gdm blocks until it -terminates. Use the Init/* script for programs that are supposed to -run alongside with the gdm login window. xconsole for -instance. Commands to set the background etc. goes in this file too. - -It is up to the sysadmin to decide whether clients started by the Init -script should be killed before starting the user session. This is -controlled with the KillInitClient option in gdm.conf. - -When the user has been successfully authenticated, gdm tries to run -the PreSession script. Similar to the Init-scripts, -PreSession/<displayname> will be executed first, if that is not found -gdm will attempt to run PreSession/Default. The script will be run as -root and gdm blocks until it terminates. Use this script for local -session management or accounting stuff. The USER environment variable -contains the login of the authenticated user. The script should return -0 on success. Any other value will cause gdm to terminate the current -login process. - -Then the session script is run. Session scripts are located in the -etc/gdm/Session directory. Which one gdm runs depends on the session -the user chose in the Sessions-menu in the gdm greeter. If no session -is selected and the user has no last session stored in his -~/.gnome/gdm file, the system will choose or first script found or -- -if Sessions/Default exists -- this will be run. For instance you can -create a symlink from Gnome to Default to make Gnome the default -desktop environment. - -When the user terminates his session the PostSession script will be -run. Operation is similar to Init and PreSession. That is, gdm will -attempt to execute the script PostSession/<displayname> and if that -doesn't exist: PostSession/Default. Again the script will be run with -root priviledges, gdm will block and the USER environment variable -will contain the name of the user who just logged out. - -Neither of the Init, PreSession or PostSession scripts are necessary -and can be left out. At least one session script is required for -proper operation. - - -3. The config file - -3.1 Section: [daemon] - -Chooser=@bindir@/gdmchooser --disable-sound - Path and name of the gdmchooser executable. - -DefaultPath=/bin:/usr/bin:/usr/bin/X11:/usr/local/bin - Specifies the path which will be set in the user's session. - -DisplayInitDir=@sysconfdir@/gdm/Init - Directory containing the Init scripts. - -Greeter=@bindir@/gdmlogin --disable-sound - Path and name of the login program executable. - -Group=gdm - The group id under which gdmlogin/gdmchooser is run. - -HaltCommand=/sbin/shutdown -h now - Command to be executed when user selects Halt from the System - menu (Full path to executable). - -KillInitClients=1 - Determines whether gdm should kill X clients started by the - Init scripts when the user logs in. Default is 1. - -LogDir=@authdir@ - Directory containing the log files for the displays. By - default this is the same as the ServAuthDir. - -PidFile=/var/run/gdm.pid - Name of the gdm daemon pidfile. - -PostSessionScriptDir=@sysconfdir@/gdm/PostSession - Directory containing the PostSession scripts. - -PreSessionScriptDir=@sysconfdir@/gdm/PreSession - Directory containing the PreSession scripts. - -RebootCommand=/sbin/shutdown -r now - Command to be executed when user selects Reboot from the - System menu. Full path is required. - -RootPath=/sbin:/usr/sbin:/bin:/usr/bin:/usr/bin/X11:/usr/local/bin - Specifies the path which will be set in the root's session and - the scripts executed by gdm. - -ServAuthDir=@authdir@ - Directory containing the X authentication files for the - displays. Should be owned by gdm.gdm with permissions 750. - -SessionDir=@sysconfdir@/gdm/Sessions - Directory containing the Session scripts. - -User=gdm - The username under which gdm is run. - -UserAuthDir= - The directory where user's .Xauthority file should be - saved. When NULL ~user is used. - -UserAuthFBDir=/tmp - If gdm fails to update user's .Xauthority file for some odd - reason a cookie is created in this directory. - -UserAuthFile=.Xauthority - Name of the file to store user cookies in. - - -3.2 Section: [security] - -AllowRoot=0 - Set to 1 to enable root logins. - -RelaxPermissions=0 - By default gdm ignores files/dirs writable to other users than - the owner. - - Changing the value of RelaxPermissions makes it possible to - alter this behaviour: - - 0 - Paranoia option. Only accepts user owned files and dirs. - 1 - Allow group writable files/dirs - 2 - Allow world writable files/dirs - -RetryDelay=3 - The number of seconds gdm should wait before reactivating the - entry field after a failed login. - -UserMaxFile=65536 - gdm will refuse to read/write files bigger than this number - (in bytes). - - In addition to the size check both gdm and gdmlogin are - extremely picky about accessing files in user directories. - Neither will follow symlinks and they can optionally refuse to - read files and directories writable by other than the owner. - -VerboseAuth=0 - Specifies whether gdm should print authentication errors. - Depending on authentication type usernames might be exposed - when this option is on. - - -3.3 Section: [xdmcp] - -Enable=0 - Setting to 1 enables XDMCP support allowing remote displays/X - terminals to be managed by gdm. - - gdm listens for requests on UDP port 177. Access from remote - displays is controlled by the TCP Wrappers library. The - service name is `gdm'. - - You should add - - gdm: .my.domain - - or something similar to /etc/hosts.allow. See the - hosts_access(5) man page for details. - - Please note that XDMCP is not a particularly secure protocol - and that it is a good idea to block UDP port 177 on your - firewall unless you really need it. - -HonorIndirect=1 - Enables INDIRECT choosing (i.e. gdmchooser) for X-terminals - which don't supply their own display browser. - -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 simultaneous displays initiating a connection. - -MaxPendingIndirect=4 - Specifies the number of remote displays that can be in choose - mode simultaneously. - -MaxSessions=16 - Determines the maximum number of remote display connections - which will be accepted. - -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 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. - -MaxWaitIndirect=30 - FIXME - -Port=177 - The UDP port number gdm should listen to for XDMCP requests. - Don't change this. - - -3.4 Section: [gui] - -Gtkrc= - Path to a gtkrc containing the theme for use in - gdmlogin/gdmchooser. - -MaxIconWidth=128 -MaxIconHeight=128 - Specifies the maximum icon sizes in the face browser. - - -3.5 Section: [greeter] - -Browser=0 - Set to 1 to enable the face browser. - -DefaultFace=@pixmapdir@/nophoto.png - Default icon file for users without a personal picture in - ~/gnome/photo. The image must be in an Imlib supported format - and it must be readable for the gdm user. - -DefaultLocale=english - This language is used for the user's session unless if nothing - is specified in ~user/.gnome/gdm. - -Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody - Comma-separated list of usernamed to exclude from the face - browser. - -Font=-adobe-helvetica-bold-r-normal-*-*-180-*-*-*-*-*-* - Font to use for the welcome message. - -GlobalFaceDir=@datadir@/faces/ - Systemwide directory for face files. The sysadmin can place - icons for users here without touching their homedirs. The - iconname represents a user name. I.e. <GlobalFaceDir>/johndoe - would contain the icon for the user johndoe (No - extension). The images must be in an Imlib supported format - and they must be readable for the gdm user. - - A user's own icon file will take precedence over the sysadmin - provided one. - -Icon=@pixmapdir@/gdm.xpm - File to use for gdmlogin when it's in iconified state. The - image must be in an Imlib supported format and it must be - readable for the gdm user. If no file is specified the - iconify feature is disabled. - -LocaleFile=@localedir@/locale.alias - File in GNU locale format with entries for all supported - languages. - -Logo=@pixmapdir@/gnome-logo-large.png - File to display in the logo box. The image must be in an - Imlib supported format and it must be readable for the gdm - user. If no file is specified the logo feature is disabled. - -Quiver=1 - Controls whether gdmgreeter should shake the display when an - incorrect username/password is entered. Default: 1. - -SystemMenu=0 - Turns the Shutdown/Halt menu on/off. Default: 0 - -Welcome=Welcome to %h - Controls which text to display next to the logo image in the - greeter. The following control chars are supported: - - %% the `%' character - %d display's hostname - %h hostname - %r release (OS version) - %s sysname (i.e. OS) - %m machine (processor type) - -3.6 Section: [chooser] - -DefaultHostImage=@pixmapdir@/nohost.png - File name for the default host icon. - -HostImageDir=@datadir@/hosts - Repository for host icon files. The sysadmin can place icons - for remote hosts here and they will appear in gdmchooser. - - The file name must match the FQDN for the host (No extension!). - Icons must be in an Imlib supported format and must be - readable to the gdm user. - -ScanTime=3 - Specifies how many seconds gdmchooser should wait for replies - to it's BROADCAST_QUERY. - - -3.7 Section: [servers] - - -0=/usr/bin/X11/X -1=/usr/bin/X11/X -bpp 8 - - Control section for local X servers. Each line indicates the - local display number and which command needs to be run to - start the X server(s). - - gdm will append "-auth <ServAuthDir>/:n.Xauth :n", where n is - the display number, to this string. - -$Id$ diff --git a/docs/gdmconfig/C/Makefile.am b/docs/gdmconfig/C/Makefile.am deleted file mode 100644 index f0d4b332..00000000 --- a/docs/gdmconfig/C/Makefile.am +++ /dev/null @@ -1,23 +0,0 @@ -figs = \ - figures/GDM_auto_login.png \ - figures/GDM_background.png \ - figures/GDM_chooser.png \ - figures/GDM_enviro.png \ - figures/GDM_face_brow.png \ - figures/GDM_full.png \ - figures/GDM_login_appear.png \ - figures/GDM_login_behav.png \ - figures/GDM_login_sessions.png \ - figures/GDM_menubar.png \ - figures/GDM_misc.png \ - figures/GDM_paths.png \ - figures/GDM_security.png \ - figures/GDM_xdmcp.png \ - figures/GDM_xserv_setup.png - -docname = gdmconfig -lang = C -omffile=gdmconfig-C.omf -sgml_ents = -include $(top_srcdir)/docs/sgmldocs.make -dist-hook: app-dist-hook diff --git a/docs/gdmconfig/C/figures/GDM_auto_login.png b/docs/gdmconfig/C/figures/GDM_auto_login.png Binary files differdeleted file mode 100644 index cdb9fe39..00000000 --- a/docs/gdmconfig/C/figures/GDM_auto_login.png +++ /dev/null diff --git a/docs/gdmconfig/C/figures/GDM_background.png b/docs/gdmconfig/C/figures/GDM_background.png Binary files differdeleted file mode 100644 index 0f092104..00000000 --- a/docs/gdmconfig/C/figures/GDM_background.png +++ /dev/null diff --git a/docs/gdmconfig/C/figures/GDM_chooser.png b/docs/gdmconfig/C/figures/GDM_chooser.png Binary files differdeleted file mode 100644 index 874ebc4f..00000000 --- a/docs/gdmconfig/C/figures/GDM_chooser.png +++ /dev/null diff --git a/docs/gdmconfig/C/figures/GDM_enviro.png b/docs/gdmconfig/C/figures/GDM_enviro.png Binary files differdeleted file mode 100644 index a01a65b7..00000000 --- a/docs/gdmconfig/C/figures/GDM_enviro.png +++ /dev/null diff --git a/docs/gdmconfig/C/figures/GDM_expert_misc.png b/docs/gdmconfig/C/figures/GDM_expert_misc.png Binary files differdeleted file mode 100644 index 8eb22136..00000000 --- a/docs/gdmconfig/C/figures/GDM_expert_misc.png +++ /dev/null diff --git a/docs/gdmconfig/C/figures/GDM_face_brow.png b/docs/gdmconfig/C/figures/GDM_face_brow.png Binary files differdeleted file mode 100644 index 8eec317f..00000000 --- a/docs/gdmconfig/C/figures/GDM_face_brow.png +++ /dev/null diff --git a/docs/gdmconfig/C/figures/GDM_full.png b/docs/gdmconfig/C/figures/GDM_full.png Binary files differdeleted file mode 100644 index 8c4ea859..00000000 --- a/docs/gdmconfig/C/figures/GDM_full.png +++ /dev/null diff --git a/docs/gdmconfig/C/figures/GDM_login_appear.png b/docs/gdmconfig/C/figures/GDM_login_appear.png Binary files differdeleted file mode 100644 index cb8c83cd..00000000 --- a/docs/gdmconfig/C/figures/GDM_login_appear.png +++ /dev/null diff --git a/docs/gdmconfig/C/figures/GDM_login_behav.png b/docs/gdmconfig/C/figures/GDM_login_behav.png Binary files differdeleted file mode 100644 index 931f684e..00000000 --- a/docs/gdmconfig/C/figures/GDM_login_behav.png +++ /dev/null diff --git a/docs/gdmconfig/C/figures/GDM_login_sessions.png b/docs/gdmconfig/C/figures/GDM_login_sessions.png Binary files differdeleted file mode 100644 index 2b0c65c5..00000000 --- a/docs/gdmconfig/C/figures/GDM_login_sessions.png +++ /dev/null diff --git a/docs/gdmconfig/C/figures/GDM_menubar.png b/docs/gdmconfig/C/figures/GDM_menubar.png Binary files differdeleted file mode 100644 index 1b0079d5..00000000 --- a/docs/gdmconfig/C/figures/GDM_menubar.png +++ /dev/null diff --git a/docs/gdmconfig/C/figures/GDM_misc.png b/docs/gdmconfig/C/figures/GDM_misc.png Binary files differdeleted file mode 100644 index 62dc1eb0..00000000 --- a/docs/gdmconfig/C/figures/GDM_misc.png +++ /dev/null diff --git a/docs/gdmconfig/C/figures/GDM_paths.png b/docs/gdmconfig/C/figures/GDM_paths.png Binary files differdeleted file mode 100644 index 2e29248b..00000000 --- a/docs/gdmconfig/C/figures/GDM_paths.png +++ /dev/null diff --git a/docs/gdmconfig/C/figures/GDM_security.png b/docs/gdmconfig/C/figures/GDM_security.png Binary files differdeleted file mode 100644 index 6fde3ff1..00000000 --- a/docs/gdmconfig/C/figures/GDM_security.png +++ /dev/null diff --git a/docs/gdmconfig/C/figures/GDM_xdmcp.png b/docs/gdmconfig/C/figures/GDM_xdmcp.png Binary files differdeleted file mode 100644 index 1194894d..00000000 --- a/docs/gdmconfig/C/figures/GDM_xdmcp.png +++ /dev/null diff --git a/docs/gdmconfig/C/figures/GDM_xserv_setup.png b/docs/gdmconfig/C/figures/GDM_xserv_setup.png Binary files differdeleted file mode 100644 index 15822bd5..00000000 --- a/docs/gdmconfig/C/figures/GDM_xserv_setup.png +++ /dev/null diff --git a/docs/gdmconfig/C/gdmconfig-C.omf b/docs/gdmconfig/C/gdmconfig-C.omf deleted file mode 100644 index faa1c4f5..00000000 --- a/docs/gdmconfig/C/gdmconfig-C.omf +++ /dev/null @@ -1,14 +0,0 @@ -<?xml version="1.0" standalone="no"?> -<omf> - <resource> - <title> - The GDM Configurator Manual - </title> - <subject> - <category>GNOME|Core Desktop</category> - </subject> - <format mime="text/sgml"/> - <identifier url="gdmconfig.sgml"/> - <language code="C"/> - </resource> -</omf> diff --git a/docs/gdmconfig/C/gdmconfig.sgml b/docs/gdmconfig/C/gdmconfig.sgml deleted file mode 100644 index 6e9bdd1b..00000000 --- a/docs/gdmconfig/C/gdmconfig.sgml +++ /dev/null @@ -1,1431 +0,0 @@ -<!DOCTYPE article PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN"[ - <!-- if not using PNG graphic, replace reference above with - .....PUBLIC "-//OASIS//DTD DocBook V3.1//EN"[ - .....PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN"[ - --> -<!ENTITY version "2.0.97.1"> -]> - -<!-- - (Do not remove this comment block.) - Maintained by the GNOME Documentation Project - http://developer.gnome.org/projects/gdp - Template version: 1.0.3 - Template last modified: Nov 16, 2000 ---> - -<article id="index"> - <artheader> - <title>Gdmconfig Manual</title> - <copyright> - <year>2001</year> - <holder>Trevor Curtis</holder> - </copyright> - - <!-- translators: uncomment this: - - <copyright> - <year>2000</year> - <holder>ME-THE-TRANSLATOR (Latin translation)</holder> - </copyright> - - --> - <!-- Use this legal notice for online documents which depend on --> - <!-- core GNOME packages. --> - <legalnotice id="legalnotice"> - <para> - Permission is granted to copy, distribute and/or modify this document - under the terms of the <ulink type="help" - url="gnome-help:fdl"><citetitle>GNU Free Documentation - License</citetitle></ulink>, Version 1.1 or any later version - published by the Free Software Foundation with no Invariant Sections, - no Front-Cover Texts, and no Back-Cover Texts. A copy of the license - can be found <ulink type="help" url="gnome-help:fdl">here</ulink>. - </para> - <para> - Many of the names used by companies to distinguish their products and - services are claimed as trademarks. Where those names appear in any - GNOME documentation, and those trademarks are made aware to the members - of the GNOME Documentation Project, the names have been printed in caps - or initial caps. - </para> - </legalnotice> - - <!-- Use this legal notice for documents which are placed on --> - <!-- the web, shipped in any way other than online documents --> - <!-- (eg. PS, PDF, or RTF), or which do not depend on the --> - <!-- core GNOME distribution. --> - <!-- --> - <!-- If you use this version, you must place the following --> - <!-- line in the document declaration at the top of your --> - <!-- document: --> - <!-- <!ENTITY FDL SYSTEM "fdl.sgml"> --> - <!-- and the following line at the bottom of your document --> - <!-- after the last </sect1>. --> - <!-- &FDL; --> - <!-- - - - <legalnotice id="legalnotice"> - <para> - Permission is granted to copy, distribute and/or modify this document - under the terms of the <link linkend="fdl"><citetitle>GNU - Free Documentation License</citetitle></link>, Version 1.1 or any later - version published by the Free Software Foundation with no Invariant - Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the - license can be found in <xref linkend="fdl">. - </para> - <para> - Many of the names used by companies to distinguish their products and - services are claimed as trademarks. Where those names appear in any - GNOME documentation, and those trademarks are made aware to the members - of the GNOME Documentation Project, the names have been printed in caps - or initial caps. - </para> - </legalnotice> - --> - - <releaseinfo> - This is version 1.0 of manual. - </releaseinfo> - -</artheader> - -<sect1 id="intro"> - <title>Introduction</title> - - <para> - <application>GDM Configurator, (GNOME Display Manager - Configurator)</application> is a configuration application - for the GDM (Gnome Display Manager). Typically, when running your - system in a - graphical login mode, the GDM is the application that facilites - logins. <application>GDM Configurator</application> allows for easy - configuration of the GDM at various levels of detail. - Customizations affect both operations and appearances. - </para> - - <para> - To run <application>GDM Configurator</application>, select - <menuchoice><guisubmenu>System</guisubmenu> - <guimenuitem>GDM Configurator</guimenuitem> - </menuchoice> - from the <guimenu>Main Menu</guimenu>, or type - <command>gdmconfig</command> on the command line. - </para> - - <note><title>Root access required</title> - <para><application>GDM Configurator</application> requires root access to - run. - </para> - </note> - - <para> - <application>GDM Configurator</application> is included in the - <filename>Gnome-Core</filename> package, which is part of the - GNOME desktop environment. This document describes version - &version; of <application>GDM Configurator</application>. - </para> -</sect1> - -<sect1 id="usage"> - <title>Using Gnome Display Manager Configurator</title> - <para> - <application>GDM Configurator</application> can be used to - change the login apperance, and behaviour as well as - security and environment options of the GDM to varying - degrees of detail. This section describes basic usage of - <application>GDM Configurator</application>. - </para> - - <sect2 id="mainwin"> - <title>Basic usage</title> - <para> - Starting <application>GDM Configure</application> opens the - <interface>Main window</interface>, shown in <xref - linkend="mainwindow-fig">. This window contains all - options relating to the GDM's configuration. - </para> - - <figure id="mainwindow-fig"> - <title>GDM Configurator Main Window</title> - <screenshot> - <screeninfo>GDM Configurator Main Window</screeninfo> - <graphic fileref="figures/GDM_full.png" format="png" srccredit="Trevor - Curtis"> - </graphic> - </screenshot> - </figure> - </sect2> - - <sect2 id="menubar"> - <title>Toolbar</title> - <para> - Toolbar Menus - </para> - - <figure id="menu-fig"> - <title>The login appearance tab</title> - <screenshot> - <screeninfo>The login appearance tab</screeninfo> - <graphic fileref="figures/GDM_menubar" format="png" srccredit="Trevor - Curtis"> - </graphic> - </screenshot> - </figure> - - <variablelist><title><guimenu>Configuration - </guimenu></title> - <varlistentry> - <term><guimenuitem>Revert settings</guimenuitem></term> - <listitem> - <para> - Reset current changes to initial settings - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Apply</guimenuitem></term> - <listitem> - <para> - Apply current changes - </para> - </listitem> - </varlistentry> - </variablelist> - - <para> - <variablelist><title><guimenu>Help</guimenu></title> - <varlistentry> - <term><guimenuitem>GDM - Configurator - users guide</guimenuitem> - </term> - <listitem> - <para>How to get this document from within <application>GDM - Configurator</application>. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>About...</guimenuitem></term> - <listitem> - <para>A little bit of kudos for all of the very hard - working guys/gals who made it all possible - </para> - </listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - - <sect2 id="options"> - <title>Options</title> - <para> - The <guilabel>Options</guilabel> box in the upper left hand - corner controls the level of detail and customization - offered on the tabs to its right. Below the Options box - is a brief description of the level chosen, and what can be - done in that level. The levels are explained below. - </para> - - <para> - <variablelist> - <varlistentry> - <term><guilabel>Basic</guilabel></term> - <listitem> - <para> - This exposes the <guilabel>Login - appearance</guilabel>, <guilabel>Login - behaviour</guilabel>, and <guilabel>Face - browser</guilabel> tabs to the right - of the <guilabel>Options</guilabel> box. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Expert</guilabel></term> - <listitem> - <para> - This exposes the <guilabel>Security</guilabel>, - <guilabel>XDMCP</guilabel>, and <guilabel>X-server - setup</guilabel> tabs to the right - of the <guilabel>Options</guilabel> box. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>System</guilabel></term> - <listitem> - <para> - This exposes the <guilabel>Paths</guilabel>, - <guilabel>Environment</guilabel>, and <guilabel> - Chooser</guilabel> tabs to the right - of the <guilabel>Options</guilabel> box. - </para> - </listitem> - </varlistentry> - </variablelist> - </para> - - <caution> - <title>Expert option and security</title> - <para> - Enabling the expert option, allows for changes in GDM's - security to be made. Improper configuration may lead to - vulnerabilities for attackers. - </para> - </caution> - <warning> - <title>System option and system health</title> - <para> - Enabling the system option, allows for very specific changes - which can impact the operation of your system. This option - is only recommended for those who know exactly what they - are doing. - </para> - </warning> - </sect2> -</sect1> - - -<sect1 id="basic"> - <title>The Basic Options</title> - <para> - Below are the options for the <guilabel>Login - appearance</guilabel>, <guilabel>Login behaviour</guilabel> - ,<guilabel>Face browser</guilabel>, and <guilabel> Automatic - login</guilabel> tabs. - </para> - <variablelist><title><guilabel>Login appearance</guilabel></title> - <varlistentry> - <term></term> - <listitem> - <figure id="loginappearance-fig"> - <title>The login appearance tab</title> - <screenshot> - <screeninfo>The login appearance tab</screeninfo> - <graphic fileref="figures/GDM_login_appear" format="png" srccredit="Trevor - Curtis"> - </graphic> - </screenshot> - </figure> - </listitem> - </varlistentry> - - <varlistentry> - <term><guibutton>Minimised Icon:</guibutton></term> - <listitem> - <para> - Change the icon that represents the login screen - when minimized. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Logo</guilabel></term> - <listitem> - <para> - Change the image that is displayed in the login - window - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Gtk+ RC file</guilabel></term> - <listitem> - <para> - Specify the location of <filename>.gtkrc</filename> - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title><guilabel>Login behaviour</guilabel></title> - <varlistentry> - <term></term> - <listitem> - <figure id="loginbehaviour-fig"> - <title>The login behaviour tab</title> - <screenshot> - <screeninfo>The login behaviour tab</screeninfo> - <graphic fileref="figures/GDM_login_behav" - format="png" srccredit="Trevor Curtis"> - </graphic> - </screenshot> - </figure> - </listitem> - </varlistentry> - <varlistentry> - <term><guibutton>Quiver on failure</guibutton></term> - <listitem> - <para> - If login fails, make the login window shake. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Exclude these users</guilabel></term> - <listitem> - <para> - Do not show the users in the user menu, on the login box. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guibutton>Default font:</guibutton></term> - <listitem> - <para> - The font to display and default to. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Welcome message</guilabel></term> - <listitem> - <para> - The text message to display in the login screen. - </para> - <note><title>Display machine name</title> - <para>To have GDM display your machine name you can - type %n in the <guilabel>Welcome message</guilabel> - field, and it will - always be replaced with whatever your machine's name - is. - </para> - </note> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Background Program</guilabel></term> - <listitem> - <para>This allows you to run a given script, or - application in the background whilst the login prompt - is displayed. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Default locale</guilabel></term> - <listitem> - <para>The locale that should be set as default in the - GDM - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guibutton>Lock position</guibutton></term> - <listitem> - <para>Lock the login box, such that it cannot be moved - within the login screen. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guibutton>Manually set - position</guibutton></term> - <listitem> - <para>Allow for the login box to be moved manually - within the login screen - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>X position</guilabel></term> - <listitem> - <para>The x coordinate for the login box placement - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Y position</guilabel></term> - <listitem> - <para>The y coordinate for the login box placement - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Xinerama screen</guilabel></term> - <listitem> - <para>This option allows one to specify on which monitor, - in a multi-monitor setup, the GDM login screen will be - displayed. - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title><guilabel>Face browser</guilabel> - </title> - <varlistentry> - <term></term> - <listitem> - <figure id="facebrowser-fig"> - <title>The face browser tab</title> - <screenshot> - <screeninfo>The face browser tab</screeninfo> - <graphic fileref="figures/GDM_face_brow" format="png" - srccredit="Trevor Curtis"> - </graphic> - </screenshot> - </figure> - </listitem> - </varlistentry> - <varlistentry> - <term>Show choosable user images</term> - <listitem> - <para>Customization of user images in the face - browser - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Default face image</guilabel></term> - <listitem> - <para>Change the image used for default users in the - face browser - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Global faces - directory</guilabel></term> - <listitem> - <para>The directory where the face images reside - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Maximum face width</guilabel></term> - <listitem> - <para>The maximum width any given face image may be - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Maximum face height</guilabel></term> - <listitem> - <para>The maximum height any given face image may be - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title><guimenu>Background</guimenu></title> - <varlistentry><term></term><listitem> - <figure id="background-fig"> - <title>The background tab</title> - <screenshot> - <screeninfo>The background tab</screeninfo> - <graphic fileref="figures/GDM_background" format="png" - srccredit="Trevor Curtis"> - </graphic> - </screenshot> - </figure> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Background type</guimenuitem></term> - <listitem> - <para> - Selection of background type. Options are backgrounds by - colour, image, or none at all. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Scale background image to fit</guilabel></term> - <listitem> - <para> - Allow an image, if selected above, to be scaled to fit alloted - space. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Only color on remote displays</guilabel></term> - <listitem> - <para> - Enable a colour to be displayed only on remote systems - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Background program</guilabel></term> - <listitem> - <para> - Allow a program to be run in the background - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title><guimenu>Automatic login</guimenu></title> - <varlistentry><term></term> - <listitem> - <figure id="autologin-fig"> - <title>The automatic login tab</title> - <screenshot> - <screeninfo>The automatic login tab</screeninfo> - <graphic fileref="figures/GDM_auto_login" format="png" - srccredit="Trevor Curtis"> - </graphic> - </screenshot> - </figure> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Login a user automatically on first bootup - </guimenuitem></term> - <listitem> - <para> - Enable logging in as the specified user when first starting - the system. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Login a user automatically after a specified - number of seconds.</guimenuitem></term> - <listitem> - <para> - Allow the GDM to automatically login after the specified number of seconds using the specified user name. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Timed login</guimenuitem></term> - <listitem> - <para> - The specified user to be used to login automaticaly. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Seconds before login</guimenuitem></term> - <listitem> - <para> - The specified number of seconds before the GDM automatically - logs in. - </para> - </listitem> - </varlistentry> - </variablelist> -</sect1> - -<sect1 id="expert"> - <title>The Expert Options</title> - <para> - Below are the options for the <guilabel>Security - </guilabel>, <guilabel>XDMCP</guilabel>, - <guilabel>X-server setup</guilabel>, <guilabel>Login sessions</guilabel>, - and <guilabel>Miscellaneous</guilabel> tabs. - </para> - <variablelist><title><guimenu>Security</guimenu></title> - <varlistentry><term></term> - <listitem> - <figure id="security-fig"> - <title>The security tab</title> - <screenshot> - <screeninfo>The security tab</screeninfo> - <graphic fileref="figures/GDM_security" format="png" - srccredit="Trevor Curtis"> - </graphic> - </screenshot> - </figure> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Allow root to login with GDM - </guimenuitem></term> - <listitem> - <para> - Allow priviledged users, such as root, to login via - the GDM. - <note> - <title>PAM supported systems</title> - <para>On systems that support PAM, this option is - ignored, and it becomes the responsiblity of the PAM - libraries to determine whether the user will be on the - local display or not. - </para> - </note> - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Kill 'init' - clients</guimenuitem></term> - <listitem> - <para> - Allow the GDM to kill X clients that start from - initialization scripts when a user logs in. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Authentication errors should be - verbose</guimenuitem></term> - <listitem> - <para> - Enable errors in authentication to be displayed to the - user(s) in the GDM display. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Permissions:</guimenuitem></term> - <listitem> - <para> - Determine the permission levels in relation to writable - directories and files of other users. The - <guimenuitem>World writable</guimenuitem> selection - allows the GDM to view world writable files and - directories. The <guimenuitem>Group - writable</guimenuitem> selection allows the GDM to - view only group writable files and - directories. Finally, the - <guimenuitem>Paranoia</guimenuitem> selection will - only accept files and directories that the user owns. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>GDM runs as this - user</guimenuitem></term> - <listitem> - <para> - Allows the GDM to be run as the specified user. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>GDM runs as this - group</guimenuitem></term> - <listitem> - <para> - Allows the GDM to be run as the specified group. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>User 'auth' - directory</guimenuitem></term> - <listitem> - <para> - Allow the directory which contains the user's .Xauthority - file to be specified - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>User 'auth' FB - directory</guimenuitem></term> - <listitem> - <para> - In case the gdm fails to update the user's .Xauthority file, - a cookie will be created in the specified directory. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>User 'auth' - File</guimenuitem></term> - <listitem> - <para> - Specify the name of the file in which to store a user's - cookies. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Retry delay</guimenuitem></term> - <listitem> - <para> - Specify the number of seconds the GDM should wait - before reactivating the entry field after a failed - login attempt. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Maximum user file length</guimenuitem></term> - <listitem> - <para> - Allows the maximum size of the largest - readable/writable file to be specified. The GDM will - refuse to read or write to a file bigger than the - given value. The value is specified in bytes. - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title>XDMCP</title> - <varlistentry><term></term><listitem> - <figure id="xdmcp-fig"> - <title>The XDMCP tab</title> - <screenshot> - <screeninfo>The XDMCP tab</screeninfo> - <graphic fileref="figures/GDM_xdmcp" format="png" - srccredit="Trevor Curtis"> - </graphic> - </screenshot> - </figure> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Enable XDMCP</guimenuitem></term> - <listitem> - <para> - Allow a remote X-terminal to request a session from - the current host. Enabling this option makes visible - the connection settings.(X Display Manager Control - Protocol) - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Honour indirect - requests</guimenuitem></term> - <listitem> - <para> - Enable choosing for X-terminals which don't supply - their own display browser. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Listen on UDP - port</guimenuitem></term> - <listitem> - <para> - Listen to UDP(user datagram protocol) requests on - the specified port. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Maximum pending - requests</guimenuitem></term> - <listitem> - <para> - Restrict the GDM to a fixed size queue of the - specified pending connections. - <warning><title>Denial of Service - Attacks</title> - <para> - This option has been included to avoid - DOS(Denial of Service Attacks). This parameter - only limits the number of allowed displays - initiating a connection at any one given time, - and does not limit the number of total remote - displays which can be managed. - </para> - </warning> - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Max pending indirect - requests</guimenuitem></term> - <listitem> - <para> - Allow only the specified number of displays with - the host chooser at any one given time. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Maximum remote - sessions</guimenuitem></term> - <listitem> - <para> - Allow only the specified number of remote displays - to be able to use the host. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Maximum wait - time</guimenuitem></term> - <listitem> - <para> - Wait for the specified amount of time in seconds - before the requesting display is removed from the - pending queue. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Maximum indirect wait - time</guimenuitem></term> - <listitem> - <para> - Wait for the specified amount of time, in seconds, - between when a display requests a chooser and the - completion of the protocol negotiation before - removing display from the pending list. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Displays per host - </guimenuitem></term> - <listitem> - <para> - Specifies the number of displays that can run on any one host to be - set. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Ping interval - </guimenuitem></term> - <listitem> - <para> - Specifies the interval, in minutes, that the gdm waits between - issuing pings to make sure the display is still alive. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem> - </guimenuitem></term> - <listitem> - <para> - Allows the specification of a script to run to set the willing - headers sent by the manager. - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title>X-server setup</title> - <varlistentry><term></term> - <listitem> - <figure id="xservsetup-fig"> - <title>The xserver setup tab</title> - <screenshot> - <screeninfo>The xserver setup tab</screeninfo> - <graphic fileref="figures/GDM_xserv_setup" format="png" - srccredit="Trevor Curtis"> - </graphic> - </screenshot> - </figure> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Servers - </guimenuitem></term> - <listitem> - <para> - Displays a list of server definitions. From the buttons on the - right, one can create aliases for a specific server setup. Enabling - a server as <guimenuoption>Flexible</guimenuoptions>, indicates that - the server can be started on demand. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Static Servers - </guimenuitem></term> - <listitem> - <para> - Allows the selection of servers which run always run. By picking - one of the server definitions via the buttons on the right, one can - setup the desired static server(s). - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Always restart X servers</guimenuitem></term> - <listitem> - <para> - Enable the X server to restart after every logout. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Standard X server - </guimenuitem></term> - <listitem> - <para> - Indicates the X server to be used and its respective path. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Xnest server - </guimenuitem></term> - <listitem> - <para> - Indicates the Xnest server to be used and its respective path. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Maximum number of flexible servers - </guimenuitem></term> - <listitem> - <para> - Indicates the maximum number of flexible servers, that may be - running at any one given time. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Failsafe X server - </guimenuitem></term> - <listitem> - <para> - Indicates the Failsafe X server to be used and its respective path. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Script to run when X is crashing - </guimenuitem></term> - <listitem> - <para> - Indicates a script to run in the event on's X session keeps crashing. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>X configurator binaries to try - </guimenuitem></term> - <listitem> - <para> - Indicates which binaries to use when an X session, or X itself, - crashes. - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title>Login sessions</title> - <varlistentry><term></term> - <listitem> - <figure id="loginsession-fig"> - <title>The Login sessions tab</title> - <screenshot> - <screeninfo>The Login sessions tab</screeninfo> - <graphic fileref="figures/GDM_login_sessions" format="png" - srccredit="Trevor Curtis"> - </graphic> - </screenshot> - </figure> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Session - directory</guimenuitem></term> - <listitem> - <para> - The directory that contains script(s) to be run at the begining - of a session - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Available Sessions</guimenuitem></term> - <listitem> - <para> - List the available sessions in which to choose from. The selected - session will appear in the <guimenuitem>Selected session name - </guimenuitem> field. Under this field, the session script is - displayed. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Gnome Chooser</guimenuitem></term> - <listitem> - <para> - If a session named Gnome is present, enable the Gnome Chooser - session to be displayed. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Gnome Failsafe</guimenuitem></term> - <listitem> - <para> - Enable the Gnome Failsafe session to be displayed. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Xterm Failsafe</guimenuitem></term> - <listitem> - <para> - Enable the Xterm Failsafe session to be displayed. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Enable debugging - output</guimenuitem></term> - <listitem> - <para> - Allow debugging information to be displayed - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Add session</guimenuitem></term> - <listitem> - <para> - Create and add a new session to be made available. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Remove session</guimenuitem></term> - <listitem> - <para> - Delete the session selected in the <guimenuitem>Available - Sessions</guimenuitem> menu. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Set as default</guimenuitem></term> - <listitem> - <para> - Enable the selected session in the <guimenuitem>Available - Sessions</guimenuitem> menu to be the default. - </para> - <note><title>Default session</title> - <para>The current default session is indicated by a light blue - highlight under the <guimenuitem>Available Sessions</guimenuitem> - menu. - </para> - </note> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title>Miscellaneous</title> - <varlistentry><term></term> - <listitem> - <figure id="misc-fig"> - <title>The Miscellaneous tab</title> - <screenshot> - <screeninfo>The Miscellaneous tab</screeninfo> - <graphic fileref="figures/GDM_expert_misc" format="png" - srccredit="Trevor Curtis"> - </graphic> - </screenshot> - </figure> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Enable debugging output</guimenuitem></term> - <listitem> - <para> - Enable the debugging output to be logged into the - syslog file. - </para> - <caution> - <title>Debug output to syslog</title> - <para> - Though a convieniant method to help track problems, this option, when - selected, can fill up a system's log files rather quickly. This is - not recommended for normal use - </para> - </caution> - </listitem> - </varlistentry> - </variablelist> - -</sect1> - -<sect1 id="system"> - <title>The System Options</title> - <para> - System menus - </para> - - <variablelist><title><guimenuitem>Paths</guimenuitem></title> - <varlistentry><term></term> - <listitem> - <figure id="paths-fig"> - <title>The paths tab</title> - <screenshot> - <screeninfo>The paths tab</screeninfo> - <graphic fileref="figures/GDM_paths" format="png" - srccredit="Trevor Curtis"> - </graphic> - </screenshot> - </figure> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Chooser - command</guimenuitem></term> - <listitem> - <para> - Allow selection and customization of the command - that will activate the chooser. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Greeter - command</guimenuitem></term> - <listitem> - <para> - Allow selection and customization of the command - that will activate the greeter. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Halt command</guimenuitem></term> - <listitem> - <para> - Allow the specified command to halt the host - machine - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Reboot - command</guimenuitem></term> - <listitem> - <para> - Allow the specified command to reboot the host - machine - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Display initialization - directory</guimenuitem></term> - <listitem> - <para> - Display the directory that contains the scripts - needed for the GDM initilization. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Logging - directory</guimenuitem></term> - <listitem> - <para> - Output logging information into a file(s) residing - in the specified directory. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Session - directory</guimenuitem></term> - <listitem> - <para> - Set the specified directory as the directory that - contains the scripts to start a session. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>PRE session scripts - directory</guimenuitem></term> - <listitem> - <para> - Look for scripts in the specified directory to run - before starting a session. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>POST session scripts - directory</guimenuitem></term> - <listitem> - <para> - Look for scripts in the specified directory to run - after ending a session. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>PID file</guimenuitem></term> - <listitem> - <para> - Place the PID file(s) in the specified directory - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title><guimenu>Environment</guimenu></title> - <varlistentry><term></term> - <listitem> - <figure id="enviro-fig"> - <title>The environment tab</title> - <screenshot> - <screeninfo>The environment tab</screeninfo> - <graphic fileref="figures/GDM_enviro" format="png" - srccredit="Trevor Curtis"> - </graphic> - </screenshot> - </figure> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Default $PATH</guimenuitem</term> - <listitem> - <para> - Set the default PATH variable ($PATH) - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Root $PATH</guimenuitem></term> - <listitem> - <para> - Set the PATH of the Root user to the specified - directories. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Locale file</guimenuitem></term> - <listitem> - <para> - Set the specified file as the main locale file. - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title><guimenu>Chooser</guimenu></title> - <varlistentry><term></term> - <listitem> - <figure id="chooser-fig"> - <title>The chooser tab</title> - <screenshot> - <screeninfo>The chooser tab</screeninfo> - <graphic fileref="figures/GDM_chooser" format="png" - srccredit="Trevor Curtis"> - </graphic> - </screenshot> - </figure> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Directory for host - images</guimenuitem></term> - <listitem> - <para> - Set the specified directory as the directory to - contain the images to represent hosts. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Default host - image</guimenuitem></term> - <listitem> - <para> - Set the selected image as the default image to - represent hosts. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Scan every 'x' - seconds</guimenuitem></term> - <listitem> - <para> - Select the number of seconds after which host images are - scanned - </para> - </listitem> - </varlistentry> - </variablelist> -</sect1> - -<sect1 id="bugs"> - <title>Known Bugs and Limitations</title> - <para> - This application has no known bugs. - </para> -</sect1> - -<sect1 id="authors"> - <title>Authors</title> - <para> - <application>GDM Configure</application> was written by Lee Mallabone - (<email>lee@fonicmonkey.net</email>). To find more information about - <application>GDM Configure</application>, please visit the <ulink - url="http://www.my-gnome-app.org" type="http">MY-GNOME-APP Web - page</ulink>. Please send all comments, suggestions, and bug - reports to the <ulink url="http://bugzilla.gnome.org" type="http">GNOME - bug tracking database</ulink>. (Instructions for submitting bug - reports can be found <ulink - url="http://bugzilla.gnome.org/Reporting.html" type="http"> - on-line</ulink>.) You can also use <application>Bug Report - Tool</application> (<command>bug-buddy</command>), available in the - <guisubmenu>Utilities</guisubmenu> submenu of <guimenu>Main - Menu</guimenu>, for submitting bug reports. - </para> - - <para> - This manual was written by Trevor Curtis - (<email>tcurtis@somaradio.ca</email>). Please send all comments and - suggestions regarding this manual to the <ulink type="http" - url="http://developer.gnome.org/projects/gdp">GNOME Documentation - Project</ulink> by sending an email to - <email>docs@gnome.org</email>. You can also add your comments - online by using the <ulink type="http" - url="http://developer.gnome.org/projects/gdp/doctable/">GNOME - Documentation Status Table</ulink>. - </para> - - <!-- For translations: uncomment this: - - <para> - Latin translation was done by ME - (<email>MYNAME@MYADDRESS</email>). Please send all comments and - suggestions regarding this translation to SOMEWHERE. - </para> - --> - -</sect1> - -<sect1 id="license"> - <title>License</title> - <para> - This program is free software; you can redistribute it and/or - modify it under the terms of the <ulink type="help" url="gnome-help:gpl"> - <citetitle>GNU General Public License</citetitle></ulink> as - published by the Free Software Foundation; - either version 2 of the License, or (at your option) any later - version. - </para> - <para> - This program is distributed in the hope that it will be useful, but - WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - <citetitle>GNU General Public License</citetitle> for more details. - </para> - <para> - A copy of the <citetitle>GNU General Public License</citetitle> is - included as an appendix to the <citetitle>GNOME Users - Guide</citetitle>. You may also obtain a copy of the - <citetitle>GNU General Public License</citetitle> from the Free - Software Foundation by visiting <ulink type="http" - url="http://www.fsf.org">their Web site</ulink> or by writing to - <address> - Free Software Foundation, Inc. - <street>59 Temple Place</street> - Suite 330 - <city>Boston</city>, <state>MA</state> <postcode>02111-1307</postcode> - <country>USA</country> - </address> - </para> -</sect1> -</article> diff --git a/docs/gdmconfig/C/gdmconfig.xml b/docs/gdmconfig/C/gdmconfig.xml deleted file mode 100644 index b6b8baa9..00000000 --- a/docs/gdmconfig/C/gdmconfig.xml +++ /dev/null @@ -1,1253 +0,0 @@ -<?xml version="1.0"?> -<!DOCTYPE article PUBLIC "-//GNOME//DTD DocBook XML V4.1.2//EN" - "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [ -<!ENTITY version "1.4.0"> <!-- replace with application version --> -<!ENTITY date "4/20/2001"> <!-- date the manual was last updated --> -<!ENTITY version "2.0.97.1"> -]> - -<!-- - (Do not remove this comment block.) - Maintained by the GNOME Documentation Project - http://developer.gnome.org/projects/gdp - Template version: 1.0.3 - Template last modified: Nov 16, 2000 ---> - -<article id="index"> - <articleinfo> - <title>Gdmconfig Manual</title> - <copyright> - <year>2001</year> - <holder>Trevor Curtis</holder> - </copyright> - - <!-- translators: uncomment this: - - <copyright> - <year>2000</year> - <holder>ME-THE-TRANSLATOR (Latin translation)</holder> - </copyright> - - --> - <!-- Use this legal notice for online documents which depend on --> - <!-- core GNOME packages. --> - <legalnotice id="legalnotice"> - <para> - Permission is granted to copy, distribute and/or modify this document - under the terms of the <ulink type="help" - url="gnome-help:fdl"><citetitle>GNU Free Documentation - License</citetitle></ulink>, Version 1.1 or any later version - published by the Free Software Foundation with no Invariant Sections, - no Front-Cover Texts, and no Back-Cover Texts. A copy of the license - can be found <ulink type="help" url="gnome-help:fdl">here</ulink>. - </para> - <para> - Many of the names used by companies to distinguish their products and - services are claimed as trademarks. Where those names appear in any - GNOME documentation, and those trademarks are made aware to the members - of the GNOME Documentation Project, the names have been printed in caps - or initial caps. - </para> - </legalnotice> - - <!-- Use this legal notice for documents which are placed on --> - <!-- the web, shipped in any way other than online documents --> - <!-- (eg. PS, PDF, or RTF), or which do not depend on the --> - <!-- core GNOME distribution. --> - <!-- --> - <!-- If you use this version, you must place the following --> - <!-- line in the document declaration at the top of your --> - <!-- document: --> - <!-- <!ENTITY FDL SYSTEM "fdl.sgml"> --> - <!-- and the following line at the bottom of your document --> - <!-- after the last </sect1>. --> - <!-- &FDL; --> - <!-- - - - <legalnotice id="legalnotice"> - <para> - Permission is granted to copy, distribute and/or modify this document - under the terms of the <link linkend="fdl"><citetitle>GNU - Free Documentation License</citetitle></link>, Version 1.1 or any later - version published by the Free Software Foundation with no Invariant - Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the - license can be found in <xref linkend="fdl">. - </para> - <para> - Many of the names used by companies to distinguish their products and - services are claimed as trademarks. Where those names appear in any - GNOME documentation, and those trademarks are made aware to the members - of the GNOME Documentation Project, the names have been printed in caps - or initial caps. - </para> - </legalnotice> - --> - - <releaseinfo> - This is version 1.0 of manual. - </releaseinfo> - -</articleinfo> - -<sect1 id="intro"> - <title>Introduction</title> - - <para> - <application>GDM Configurator, (GNOME Display Manager - Configurator)</application> is a configuration application - for the GDM (Gnome Display Manager). Typically, when running your - system in a - graphical login mode, the GDM is the application that facilites - logins. <application>GDM Configurator</application> allows for easy - configuration of the GDM at various levels of detail. - Customizations affect both operations and appearances. - </para> - - <para> - To run <application>GDM Configurator</application>, select - <menuchoice><guisubmenu>System</guisubmenu> - <guimenuitem>GDM Configurator</guimenuitem> - </menuchoice> - from the <guimenu>Main Menu</guimenu>, or type - <command>gdmconfig</command> on the command line. - </para> - - <note><title>Root access required</title> - <para><application>GDM Configurator</application> requires root access to - run. - </para> - </note> - - <para> - <application>GDM Configurator</application> is included in the - <filename>Gnome-Core</filename> package, which is part of the - GNOME desktop environment. This document describes version - &version; of <application>GDM Configurator</application>. - </para> -</sect1> - -<sect1 id="usage"> - <title>Using Gnome Display Manager Configurator</title> - <para> - <application>GDM Configurator</application> can be used to - change the login apperance, and behaviour as well as - security and environment options of the GDM to varying - degrees of detail. This section describes basic usage of - <application>GDM Configurator</application>. - </para> - - <sect2 id="mainwin"> - <title>Basic usage</title> - <para> - Starting GDM Configure opens the - Main window, shown in - This window contains all - options relating to the GDM's configuration. - </para> - -<!-- Screenshot --> - -<!-- <sect2 id="menubar"> --> - <para> - Toolbar Menus - </para> - - <!-- Screenshot --> - - <variablelist><title><guimenu>Configuration - </guimenu></title> - <varlistentry> - <term><guimenuitem>Revert settings</guimenuitem></term> - <listitem> - <para> - Reset current changes to initial settings - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Apply</guimenuitem></term> - <listitem> - <para> - Apply current changes - </para> - </listitem> - </varlistentry> - </variablelist> - - <para> - <variablelist><title><guimenu>Help</guimenu></title> - <varlistentry> - <term><guimenuitem>GDM - Configurator - users guide</guimenuitem> - </term> - <listitem> - <para>How to get this document from within <application>GDM - Configurator</application>. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>About...</guimenuitem></term> - <listitem> - <para>A little bit of kudos for all of the very hard - working guys/gals who made it all possible - </para> - </listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - - <sect2 id="options"> - <title>Options</title> - <para> - The <guilabel>Options</guilabel> box in the upper left hand - corner controls the level of detail and customization - offered on the tabs to its right. Below the Options box - is a brief description of the level chosen, and what can be - done in that level. The levels are explained below. - </para> - - <para> - <variablelist> - <varlistentry> - <term><guilabel>Basic</guilabel></term> - <listitem> - <para> - This exposes the <guilabel>Login - appearance</guilabel>, <guilabel>Login - behaviour</guilabel>, and <guilabel>Face - browser</guilabel> tabs to the right - of the <guilabel>Options</guilabel> box. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Expert</guilabel></term> - <listitem> - <para> - This exposes the <guilabel>Security</guilabel>, - <guilabel>XDMCP</guilabel>, and <guilabel>X-server - setup</guilabel> tabs to the right - of the <guilabel>Options</guilabel> box. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>System</guilabel></term> - <listitem> - <para> - This exposes the <guilabel>Paths</guilabel>, - <guilabel>Environment</guilabel>, and <guilabel> - Chooser</guilabel> tabs to the right - of the <guilabel>Options</guilabel> box. - </para> - </listitem> - </varlistentry> - </variablelist> - </para> - - <caution> - <title>Expert option and security</title> - <para> - Enabling the expert option, allows for changes in GDM's - security to be made. Improper configuration may lead to - vulnerabilities for attackers. - </para> - </caution> - <warning> - <title>System option and system health</title> - <para> - Enabling the system option, allows for very specific changes - which can impact the operation of your system. This option - is only recommended for those who know exactly what they - are doing. - </para> - </warning> - </sect2> -</sect1> - - -<sect1 id="basic"> - <title>The Basic Options</title> - <para> - Below are the options for the <guilabel>Login - appearance</guilabel>, <guilabel>Login behaviour</guilabel> - ,<guilabel>Face browser</guilabel>, and <guilabel> Automatic - login</guilabel> tabs. - </para> - <variablelist><title><guilabel>Login appearance</guilabel></title> -<!-- Screenshot --> - - <varlistentry> - <term><guibutton>Minimised Icon:</guibutton></term> - <listitem> - <para> - Change the icon that represents the login screen - when minimized. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Logo</guilabel></term> - <listitem> - <para> - Change the image that is displayed in the login - window - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Gtk+ RC file</guilabel></term> - <listitem> - <para> - Specify the location of <filename>.gtkrc</filename> - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title><guilabel>Login behaviour</guilabel></title> -<!-- Screenshot --> - <varlistentry> - <term><guibutton>Quiver on failure</guibutton></term> - <listitem> - <para> - If login fails, make the login window shake. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Exclude these users</guilabel></term> - <listitem> - <para> - Do not show the users in the user menu, on the login box. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guibutton>Default font:</guibutton></term> - <listitem> - <para> - The font to display and default to. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Welcome message</guilabel></term> - <listitem> - <para> - The text message to display in the login screen. - </para> - <note><title>Display machine name</title> - <para>To have GDM display your machine name you can - type %n in the <guilabel>Welcome message</guilabel> - field, and it will - always be replaced with whatever your machine's name - is. - </para> - </note> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Background Program</guilabel></term> - <listitem> - <para>This allows you to run a given script, or - application in the background whilst the login prompt - is displayed. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Default locale</guilabel></term> - <listitem> - <para>The locale that should be set as default in the - GDM - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guibutton>Lock position</guibutton></term> - <listitem> - <para>Lock the login box, such that it cannot be moved - within the login screen. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guibutton>Manually set - position</guibutton></term> - <listitem> - <para>Allow for the login box to be moved manually - within the login screen - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>X position</guilabel></term> - <listitem> - <para>The x coordinate for the login box placement - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Y position</guilabel></term> - <listitem> - <para>The y coordinate for the login box placement - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Xinerama screen</guilabel></term> - <listitem> - <para>This option allows one to specify on which monitor, - in a multi-monitor setup, the GDM login screen will be - displayed. - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title><guilabel>Face browser</guilabel> - </title> -<!-- Screenshot --> - <varlistentry> - <term>Show choosable user images</term> - <listitem> - <para>Customization of user images in the face - browser - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Default face image</guilabel></term> - <listitem> - <para>Change the image used for default users in the - face browser - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Global faces - directory</guilabel></term> - <listitem> - <para>The directory where the face images reside - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Maximum face width</guilabel></term> - <listitem> - <para>The maximum width any given face image may be - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Maximum face height</guilabel></term> - <listitem> - <para>The maximum height any given face image may be - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title><guimenu>Background</guimenu></title> -<!-- Screenshot --> - <varlistentry> - <term><guimenuitem>Background type</guimenuitem></term> - <listitem> - <para> - Selection of background type. Options are backgrounds by - colour, image, or none at all. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Scale background image to fit</guilabel></term> - <listitem> - <para> - Allow an image, if selected above, to be scaled to fit alloted - space. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Only color on remote displays</guilabel></term> - <listitem> - <para> - Enable a colour to be displayed only on remote systems - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Background program</guilabel></term> - <listitem> - <para> - Allow a program to be run in the background - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title><guimenu>Automatic login</guimenu></title> -<!-- Screenshot --> - <varlistentry> - <term><guimenuitem>Login a user automatically on first bootup - </guimenuitem></term> - <listitem> - <para> - Enable logging in as the specified user when first starting - the system. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Login a user automatically after a specified - number of seconds.</guimenuitem></term> - <listitem> - <para> - Allow the GDM to automatically login after the specified number of seconds using the specified user name. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Timed login</guimenuitem></term> - <listitem> - <para> - The specified user to be used to login automaticaly. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Seconds before login</guimenuitem></term> - <listitem> - <para> - The specified number of seconds before the GDM automatically - logs in. - </para> - </listitem> - </varlistentry> - </variablelist> -</sect1> - -<sect1 id="expert"> - <title>The Expert Options</title> - <para> - Below are the options for the <guilabel>Security - </guilabel>, <guilabel>XDMCP</guilabel>, - <guilabel>X-server setup</guilabel>, <guilabel>Login sessions</guilabel>, - and <guilabel>Miscellaneous</guilabel> tabs. - </para> - <variablelist><title><guimenu>Security</guimenu></title> -<!-- Screenshot --> - <varlistentry> - <term><guimenuitem>Allow root to login with GDM - </guimenuitem></term> - <listitem> - <para> - Allow priviledged users, such as root, to login via - the GDM. - <note> - <title>PAM supported systems</title> - <para>On systems that support PAM, this option is - ignored, and it becomes the responsiblity of the PAM - libraries to determine whether the user will be on the - local display or not. - </para> - </note> - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Kill 'init' - clients</guimenuitem></term> - <listitem> - <para> - Allow the GDM to kill X clients that start from - initialization scripts when a user logs in. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Authentication errors should be - verbose</guimenuitem></term> - <listitem> - <para> - Enable errors in authentication to be displayed to the - user(s) in the GDM display. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Permissions:</guimenuitem></term> - <listitem> - <para> - Determine the permission levels in relation to writable - directories and files of other users. The - <guimenuitem>World writable</guimenuitem> selection - allows the GDM to view world writable files and - directories. The <guimenuitem>Group - writable</guimenuitem> selection allows the GDM to - view only group writable files and - directories. Finally, the - <guimenuitem>Paranoia</guimenuitem> selection will - only accept files and directories that the user owns. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>GDM runs as this - user</guimenuitem></term> - <listitem> - <para> - Allows the GDM to be run as the specified user. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>GDM runs as this - group</guimenuitem></term> - <listitem> - <para> - Allows the GDM to be run as the specified group. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>User 'auth' - directory</guimenuitem></term> - <listitem> - <para> - Allow the directory which contains the user's .Xauthority - file to be specified - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>User 'auth' FB - directory</guimenuitem></term> - <listitem> - <para> - In case the gdm fails to update the user's .Xauthority file, - a cookie will be created in the specified directory. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>User 'auth' - File</guimenuitem></term> - <listitem> - <para> - Specify the name of the file in which to store a user's - cookies. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Retry delay</guimenuitem></term> - <listitem> - <para> - Specify the number of seconds the GDM should wait - before reactivating the entry field after a failed - login attempt. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Maximum user file length</guimenuitem></term> - <listitem> - <para> - Allows the maximum size of the largest - readable/writable file to be specified. The GDM will - refuse to read or write to a file bigger than the - given value. The value is specified in bytes. - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title>XDMCP</title> -<!-- Screenshot --> - <varlistentry> - <term><guimenuitem>Enable XDMCP</guimenuitem></term> - <listitem> - <para> - Allow a remote X-terminal to request a session from - the current host. Enabling this option makes visible - the connection settings.(X Display Manager Control - Protocol) - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Honour indirect - requests</guimenuitem></term> - <listitem> - <para> - Enable choosing for X-terminals which don't supply - their own display browser. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Listen on UDP - port</guimenuitem></term> - <listitem> - <para> - Listen to UDP(user datagram protocol) requests on - the specified port. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Maximum pending - requests</guimenuitem></term> - <listitem> - <para> - Restrict the GDM to a fixed size queue of the - specified pending connections. - <warning><title>Denial of Service - Attacks</title> - <para> - This option has been included to avoid - DOS(Denial of Service Attacks). This parameter - only limits the number of allowed displays - initiating a connection at any one given time, - and does not limit the number of total remote - displays which can be managed. - </para> - </warning> - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Max pending indirect - requests</guimenuitem></term> - <listitem> - <para> - Allow only the specified number of displays with - the host chooser at any one given time. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Maximum remote - sessions</guimenuitem></term> - <listitem> - <para> - Allow only the specified number of remote displays - to be able to use the host. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Maximum wait - time</guimenuitem></term> - <listitem> - <para> - Wait for the specified amount of time in seconds - before the requesting display is removed from the - pending queue. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Maximum indirect wait - time</guimenuitem></term> - <listitem> - <para> - Wait for the specified amount of time, in seconds, - between when a display requests a chooser and the - completion of the protocol negotiation before - removing display from the pending list. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Displays per host - </guimenuitem></term> - <listitem> - <para> - Specifies the number of displays that can run on any one host to be - set. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Ping interval - </guimenuitem></term> - <listitem> - <para> - Specifies the interval, in minutes, that the gdm waits between - issuing pings to make sure the display is still alive. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem> - </guimenuitem></term> - <listitem> - <para> - Allows the specification of a script to run to set the willing - headers sent by the manager. - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title>X-server setup</title> -<!-- Screenshot --> - <varlistentry> - <term><guimenuitem>Servers - </guimenuitem></term> - <listitem> - <para> - Displays a list of server definitions. From the buttons on the - right, one can create aliases for a specific server setup. Enabling - a server as <guimenuitem>Flexible</guimenuitem>, indicates that - the server can be started on demand. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Static Servers - </guimenuitem></term> - <listitem> - <para> - Allows the selection of servers which run always run. By picking - one of the server definitions via the buttons on the right, one can - setup the desired static server(s). - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Always restart X servers</guimenuitem></term> - <listitem> - <para> - Enable the X server to restart after every logout. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Standard X server - </guimenuitem></term> - <listitem> - <para> - Indicates the X server to be used and its respective path. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Xnest server - </guimenuitem></term> - <listitem> - <para> - Indicates the Xnest server to be used and its respective path. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Maximum number of flexible servers - </guimenuitem></term> - <listitem> - <para> - Indicates the maximum number of flexible servers, that may be - running at any one given time. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Failsafe X server - </guimenuitem></term> - <listitem> - <para> - Indicates the Failsafe X server to be used and its respective path. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Script to run when X is crashing - </guimenuitem></term> - <listitem> - <para> - Indicates a script to run in the event on's X session keeps crashing. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>X configurator binaries to try - </guimenuitem></term> - <listitem> - <para> - Indicates which binaries to use when an X session, or X itself, - crashes. - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title>Login sessions</title> - <varlistentry> - <term><guimenuitem>Session - directory</guimenuitem></term> - <listitem> - <para> - The directory that contains script(s) to be run at the begining - of a session - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Available Sessions</guimenuitem></term> - <listitem> - <para> - List the available sessions in which to choose from. The selected - session will appear in the <guimenuitem>Selected session name - </guimenuitem> field. Under this field, the session script is - displayed. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Gnome Chooser</guimenuitem></term> - <listitem> - <para> - If a session named Gnome is present, enable the Gnome Chooser - session to be displayed. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Gnome Failsafe</guimenuitem></term> - <listitem> - <para> - Enable the Gnome Failsafe session to be displayed. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Xterm Failsafe</guimenuitem></term> - <listitem> - <para> - Enable the Xterm Failsafe session to be displayed. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Enable debugging - output</guimenuitem></term> - <listitem> - <para> - Allow debugging information to be displayed - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Add session</guimenuitem></term> - <listitem> - <para> - Create and add a new session to be made available. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Remove session</guimenuitem></term> - <listitem> - <para> - Delete the session selected in the <guimenuitem>Available - Sessions</guimenuitem> menu. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Set as default</guimenuitem></term> - <listitem> - <para> - Enable the selected session in the <guimenuitem>Available - Sessions</guimenuitem> menu to be the default. - </para> - <note><title>Default session</title> - <para>The current default session is indicated by a light blue - highlight under the <guimenuitem>Available Sessions</guimenuitem> - menu. - </para> - </note> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title>Miscellaneous</title> - <varlistentry> - <term><guimenuitem>Enable debugging output</guimenuitem></term> - <listitem> - <para> - Enable the debugging output to be logged into the - syslog file. - </para> - <caution> - <title>Debug output to syslog</title> - <para> - Though a convieniant method to help track problems, this option, when - selected, can fill up a system's log files rather quickly. This is - not recommended for normal use - </para> - </caution> - </listitem> - </varlistentry> - </variablelist> - -</sect1> - -<sect1 id="system"> - <title>The System Options</title> - <para> - System menus - </para> - - <variablelist><title><guimenuitem>Paths</guimenuitem></title> - <!-- Screenshot --> - <varlistentry> - <term><guimenuitem>Chooser - command</guimenuitem></term> - <listitem> - <para> - Allow selection and customization of the command - that will activate the chooser. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Greeter - command</guimenuitem></term> - <listitem> - <para> - Allow selection and customization of the command - that will activate the greeter. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Halt command</guimenuitem></term> - <listitem> - <para> - Allow the specified command to halt the host - machine - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Reboot - command</guimenuitem></term> - <listitem> - <para> - Allow the specified command to reboot the host - machine - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Display initialization - directory</guimenuitem></term> - <listitem> - <para> - Display the directory that contains the scripts - needed for the GDM initilization. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Logging - directory</guimenuitem></term> - <listitem> - <para> - Output logging information into a file(s) residing - in the specified directory. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Session - directory</guimenuitem></term> - <listitem> - <para> - Set the specified directory as the directory that - contains the scripts to start a session. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>PRE session scripts - directory</guimenuitem></term> - <listitem> - <para> - Look for scripts in the specified directory to run - before starting a session. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>POST session scripts - directory</guimenuitem></term> - <listitem> - <para> - Look for scripts in the specified directory to run - after ending a session. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>PID file</guimenuitem></term> - <listitem> - <para> - Place the PID file(s) in the specified directory - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title><guimenu>Environment</guimenu></title> - <varlistentry> - <term><guimenuitem>Default $PATH</guimenuitem></term> - <listitem> - <para> - Set the default PATH variable ($PATH) - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Root $PATH</guimenuitem></term> - <listitem> - <para> - Set the PATH of the Root user to the specified - directories. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Locale file</guimenuitem></term> - <listitem> - <para> - Set the specified file as the main locale file. - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist><title><guimenu>Chooser</guimenu></title> -<!-- Screenshot --> - <varlistentry> - <term><guimenuitem>Directory for host - images</guimenuitem></term> - <listitem> - <para> - Set the specified directory as the directory to - contain the images to represent hosts. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Default host - image</guimenuitem></term> - <listitem> - <para> - Set the selected image as the default image to - represent hosts. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Scan every 'x' - seconds</guimenuitem></term> - <listitem> - <para> - Select the number of seconds after which host images are - scanned - </para> - </listitem> - </varlistentry> - </variablelist> -</sect1> - -<sect1 id="bugs"> - <title>Known Bugs and Limitations</title> - <para> - This application has no known bugs. - </para> -</sect1> - -<sect1 id="authors"> - <title>Authors</title> - <para> - <application>GDM Configure</application> was written by Lee Mallabone - (<email>lee@fonicmonkey.net</email>). To find more information about - <application>GDM Configure</application>, please visit the <ulink - url="http://www.my-gnome-app.org" type="http">MY-GNOME-APP Web - page</ulink>. Please send all comments, suggestions, and bug - reports to the <ulink url="http://bugzilla.gnome.org" type="http">GNOME - bug tracking database</ulink>. (Instructions for submitting bug - reports can be found <ulink - url="http://bugzilla.gnome.org/Reporting.html" type="http"> - on-line</ulink>.) You can also use <application>Bug Report - Tool</application> (<command>bug-buddy</command>), available in the - <guisubmenu>Utilities</guisubmenu> submenu of <guimenu>Main - Menu</guimenu>, for submitting bug reports. - </para> - - <para> - This manual was written by Trevor Curtis - (<email>tcurtis@somaradio.ca</email>). Please send all comments and - suggestions regarding this manual to the <ulink type="http" - url="http://developer.gnome.org/projects/gdp">GNOME Documentation - Project</ulink> by sending an email to - <email>docs@gnome.org</email>. You can also add your comments - online by using the <ulink type="http" - url="http://developer.gnome.org/projects/gdp/doctable/">GNOME - Documentation Status Table</ulink>. - </para> - - <!-- For translations: uncomment this: - - <para> - Latin translation was done by ME - (<email>MYNAME@MYADDRESS</email>). Please send all comments and - suggestions regarding this translation to SOMEWHERE. - </para> - --> - -</sect1> - -<sect1 id="license"> - <title>License</title> - <para> - This program is free software; you can redistribute it and/or - modify it under the terms of the <ulink type="help" url="gnome-help:gpl"> - <citetitle>GNU General Public License</citetitle></ulink> as - published by the Free Software Foundation; - either version 2 of the License, or (at your option) any later - version. - </para> - <para> - This program is distributed in the hope that it will be useful, but - WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - <citetitle>GNU General Public License</citetitle> for more details. - </para> - <para> - A copy of the <citetitle>GNU General Public License</citetitle> is - included as an appendix to the <citetitle>GNOME Users - Guide</citetitle>. You may also obtain a copy of the - <citetitle>GNU General Public License</citetitle> from the Free - Software Foundation by visiting <ulink type="http" - url="http://www.fsf.org">their Web site</ulink> or by writing to - <address> - Free Software Foundation, Inc. - <street>59 Temple Place</street> - Suite 330 - <city>Boston</city>, <state>MA</state> <postcode>02111-1307</postcode> - <country>USA</country> - </address> - </para> -</sect1> -</article> diff --git a/docs/gdmconfig/C/topic.dat b/docs/gdmconfig/C/topic.dat deleted file mode 100644 index 67004b6f..00000000 --- a/docs/gdmconfig/C/topic.dat +++ /dev/null @@ -1 +0,0 @@ -index.html GDM Configurator users guide. diff --git a/docs/gdmconfig/Makefile.am b/docs/gdmconfig/Makefile.am deleted file mode 100644 index 42ffacc2..00000000 --- a/docs/gdmconfig/Makefile.am +++ /dev/null @@ -1 +0,0 @@ -SUBDIRS = C diff --git a/docs/sgmldocs.make b/docs/sgmldocs.make deleted file mode 100644 index 8159f7df..00000000 --- a/docs/sgmldocs.make +++ /dev/null @@ -1,138 +0,0 @@ -# To use this template: -# 1) Define: figs, docname, lang, omffile, sgml_ents although figs, -# omffile, and sgml_ents may be empty in your Makefile.am which -# will "include" this one -# 2) Figures must go under figures/ and be in PNG format -# 3) You should only have one document per directory -# -# Note that this makefile forces the directory name under -# $prefix/share/gnome/help/ to be the same as the SGML filename -# of the document. This is required by GNOME. eg: -# $prefix/share/gnome/help/fish_applet/C/fish_applet.sgml -# ^^^^^^^^^^^ ^^^^^^^^^^^ -# Definitions: -# figs A list of screenshots which will be included in EXTRA_DIST -# Note that these should reside in figures/ and should be .png -# files, or you will have to make modifications below. -# docname This is the name of the SGML file: <docname>.sgml -# lang This is the document locale -# omffile This is the name of the OMF file. Convention is to name -# it <docname>-<locale>.omf. -# sgml_ents This is a list of SGML entities which must be installed -# with the main SGML file and included in EXTRA_DIST. -# eg: -# figs = \ -# figures/fig1.png \ -# figures/fig2.png -# docname = scrollkeeper-manual -# lang = C -# omffile=scrollkeeper-manual-C.omf -# sgml_ents = fdl.sgml -# include $(top_srcdir)/help/sgmldocs.make -# dist-hook: app-dist-hook -# - -docdir = $(datadir)/gnome/help/$(docname)/$(lang) - -doc_DATA = index.html - -sgml_files = $(sgml_ents) $(docname).sgml - -omf_dir=$(top_srcdir)/omf-install - -EXTRA_DIST = $(sgml_files) $(doc_DATA) $(omffile) $(figs) - -CLEANFILES = omf_timestamp - -all: index.html omf - -omf: omf_timestamp - -omf_timestamp: $(omffile) - -for file in $(omffile); do \ - scrollkeeper-preinstall $(docdir)/$(docname).sgml $$file $(omf_dir)/$$file; \ - done - touch omf_timestamp - -index.html: $(docname)/index.html - -cp $(docname)/index.html . - -$(docname).sgml: $(sgml_ents) - -ourdir=`pwd`; \ - cd $(srcdir); \ - cp $(sgml_ents) $$ourdir - - -# The weird srcdir trick is because the db2html from the Cygnus RPMs -# cannot handle relative filenames -$(docname)/index.html: $(srcdir)/$(docname).sgml - -srcdir=`cd $(srcdir) && pwd`; \ - if test "$(HAVE_JW)" = 'yes' ; then \ - jw -c /etc/sgml/catalog $$srcdir/$(docname).sgml -o $$srcdir/$(docname); \ - else \ - db2html $$srcdir/$(docname).sgml; \ - fi - -app-dist-hook: index.html - -$(mkinstalldirs) $(distdir)/$(docname)/stylesheet-images - -$(mkinstalldirs) $(distdir)/figures - -cp $(srcdir)/$(docname)/*.html $(distdir)/$(docname) - -for file in $(srcdir)/$(docname)/*.css; do \ - basefile=`echo $$file | sed -e 's,^.*/,,'`; \ - cp $$file $(distdir)/$(docname)/$$basefile ; \ - done - -for file in $(srcdir)/$(docname)/stylesheet-images/*.gif; do \ - basefile=`echo $$file | sed -e 's,^.*/,,'`; \ - cp $$file $(distdir)/$(docname)/stylesheet-images/$$basefile ; \ - done - -if [ -e topic.dat ]; then \ - cp $(srcdir)/topic.dat $(distdir); \ - fi - -install-data-am: index.html omf - -$(mkinstalldirs) $(DESTDIR)$(docdir)/stylesheet-images - -$(mkinstalldirs) $(DESTDIR)$(docdir)/figures - -cp $(srcdir)/$(sgml_files) $(DESTDIR)$(docdir) - -for file in $(srcdir)/$(docname)/*.html $(srcdir)/$(docname)/*.css; do \ - basefile=`echo $$file | sed -e 's,^.*/,,'`; \ - $(INSTALL_DATA) $$file $(DESTDIR)$(docdir)/$$basefile; \ - done - -for file in $(srcdir)/figures/*.png; do \ - basefile=`echo $$file | sed -e 's,^.*/,,'`; \ - $(INSTALL_DATA) $$file $(DESTDIR)$(docdir)/figures/$$basefile; \ - done - -for file in $(srcdir)/$(docname)/stylesheet-images/*.gif; do \ - basefile=`echo $$file | sed -e 's,^.*/,,'`; \ - $(INSTALL_DATA) $$file $(DESTDIR)$(docdir)/stylesheet-images/$$basefile; \ - done - -if [ -e $(srcdir)/topic.dat ]; then \ - $(INSTALL_DATA) $(srcdir)/topic.dat $(DESTDIR)$(docdir); \ - fi - -$(docname).ps: $(srcdir)/$(docname).sgml - -srcdir=`cd $(srcdir) && pwd`; \ - db2ps $$srcdir/$(docname).sgml - -$(docname).rtf: $(srcdir)/$(docname).sgml - -srcdir=`cd $(srcdir) && pwd`; \ - db2ps $$srcdir/$(docname).sgml - -uninstall-local: - -for file in $(srcdir)/$(docname)/stylesheet-images/*.gif; do \ - basefile=`echo $$file | sed -e 's,^.*/,,'`; \ - rm -f $(docdir)/stylesheet-images/$$basefile; \ - done - -for file in $(srcdir)/figures/*.png; do \ - basefile=`echo $$file | sed -e 's,^.*/,,'`; \ - rm -f $(docdir)/figures/$$basefile; \ - done - -for file in $(srcdir)/$(docname)/*.html $(srcdir)/$(docname)/*.css; do \ - basefile=`echo $$file | sed -e 's,^.*/,,'`; \ - rm -f $(DESTDIR)$(docdir)/$$basefile; \ - done - -for file in $(sgml_files); do \ - rm -f $(DESTDIR)$(docdir)/$$file; \ - done - -rmdir $(DESTDIR)$(docdir)/stylesheet-images - -rmdir $(DESTDIR)$(docdir)/figures - -rmdir $(DESTDIR)$(docdir) diff --git a/gdm.spec.in b/gdm.spec.in index 4081ac6c..a770ce6a 100644 --- a/gdm.spec.in +++ b/gdm.spec.in @@ -116,7 +116,8 @@ exit 0 %{_datadir}/applications/* %{_datadir}/gnome/capplets/* # DOCUMENTATION! -# %{_datadir}/omf/gdm +%{_datadir}/omf/gdm +%{_datadir}/gnome/help/gdm # %config %{sysconfdir}/security/console.apps/gdmsetup # %config %{sysconfdir}/X11/gdm/gnomerc # %config %{sysconfdir}/X11/gdm/gdm.conf diff --git a/gui/gdmlogin.c b/gui/gdmlogin.c index 6ffa254e..6cde3023 100644 --- a/gui/gdmlogin.c +++ b/gui/gdmlogin.c @@ -3121,8 +3121,8 @@ gdm_login_gui_init (void) NULL); gtk_widget_show (GTK_WIDGET (item)); gtk_tooltips_set_tip (tooltips, GTK_WIDGET (item), - _("Shut down your computer so that " - "you may turn it off."), + _("Shut down the system so that " + "you may safely turn off the computer."), NULL); got_anything = TRUE; } diff --git a/gui/gdmphotosetup.c b/gui/gdmphotosetup.c index 9813c6b7..da1108c3 100644 --- a/gui/gdmphotosetup.c +++ b/gui/gdmphotosetup.c @@ -22,6 +22,7 @@ #include <libgnome/libgnome.h> #include <libgnomeui/libgnomeui.h> #include <sys/types.h> +#include <signal.h> #include <sys/stat.h> #include <fcntl.h> #include <errno.h> diff --git a/gui/gdmsetup.c b/gui/gdmsetup.c index 19b9b20a..47f5f920 100644 --- a/gui/gdmsetup.c +++ b/gui/gdmsetup.c @@ -1318,6 +1318,55 @@ find_tar (void) } static char * +find_chmod (void) +{ + char *chmod_prog; + char *try[] = { + "/bin/chmod", + "/sbin/chmod", + "/usr/bin/chmod", + "/usr/sbin/chmod", + NULL }; + int i; + + chmod_prog = g_find_program_in_path ("chmod"); + if (chmod_prog != NULL) + return chmod_prog; + + for (i = 0; try[i] != NULL; i++) { + if (access (try[i], X_OK) == 0) + return g_strdup (try[i]); + } + /* Hmmm, fallback */ + return g_strdup ("/bin/chmod"); +} + +static char * +find_chown (void) +{ + char *chown_prog; + char *try[] = { + "/bin/chown", + "/sbin/chown", + "/usr/bin/chown", + "/usr/sbin/chown", + NULL }; + int i; + + chown_prog = g_find_program_in_path ("chown"); + if (chown_prog != NULL) + return chown_prog; + + for (i = 0; try[i] != NULL; i++) { + if (access (try[i], X_OK) == 0) + return g_strdup (try[i]); + } + /* Hmmm, fallback */ + return g_strdup ("/bin/chown"); +} + + +static char * get_the_dir (FILE *fp, char **error) { char buf[2048]; @@ -1551,13 +1600,14 @@ install_ok (GtkWidget *button, gpointer data) char *fname = g_filename_to_utf8 (dir, -1, NULL, NULL, NULL); char *s; GtkWidget *button; + GtkWidget *dlg; + /* FIXME: if exists already perhaps we could also have an * option to change the dir name */ s = g_strdup_printf (_("Theme directory '%s' seems to be already " "installed, install again anyway?"), fname); - GtkWidget *dlg = - ve_hig_dialog_new + dlg = ve_hig_dialog_new (GTK_WINDOW (fs), GTK_DIALOG_MODAL | GTK_DIALOG_DESTROY_WITH_PARENT, @@ -1599,22 +1649,26 @@ install_ok (GtkWidget *button, gpointer data) if (system (untar_cmd) == 0) { char *cmd; char *quoted = g_shell_quote (dir); + char *chown = find_chown (); + char *chmod = find_chmod (); success = TRUE; /* HACK! */ - cmd = g_strdup_printf ("/bin/chown -R root.root %s", quoted); + cmd = g_strdup_printf ("%s -R root.root %s", chown, quoted); system (cmd); g_free (cmd); - cmd = g_strdup_printf ("/bin/chmod -R a+r %s", quoted); + cmd = g_strdup_printf ("%s -R a+r %s", chmod, quoted); system (cmd); g_free (cmd); - cmd = g_strdup_printf ("/bin/chmod a+x %s", quoted); + cmd = g_strdup_printf ("%s a+x %s", chmod, quoted); system (cmd); g_free (cmd); g_free (quoted); + g_free (chown); + g_free (chmod); } chdir (cwd); } diff --git a/gui/greeter/Makefile.am b/gui/greeter/Makefile.am index bb51f2ce..cd151c27 100644 --- a/gui/greeter/Makefile.am +++ b/gui/greeter/Makefile.am @@ -47,6 +47,8 @@ gdmgreeter_SOURCES = \ greeter_item_pam.h \ greeter_item_ulist.c \ greeter_item_ulist.h \ + greeter_item_customlist.c \ + greeter_item_customlist.h \ greeter_parser.c \ greeter_parser.h \ greeter_session.c \ diff --git a/gui/greeter/greeter.c b/gui/greeter/greeter.c index 8332b142..80b86c1e 100644 --- a/gui/greeter/greeter.c +++ b/gui/greeter/greeter.c @@ -23,6 +23,7 @@ #include "greeter_item_clock.h" #include "greeter_item_pam.h" #include "greeter_item_ulist.h" +#include "greeter_item_customlist.h" #include "greeter_item_capslock.h" #include "greeter_item_timed.h" #include "greeter_events.h" @@ -71,6 +72,7 @@ int GdmMinimalUID; gboolean GdmAllowRoot; gboolean GdmAllowRemoteRoot; gchar *GdmWelcome; +gchar *GdmServAuthDir; gboolean GdmUseCirclesInEntry = FALSE; @@ -141,6 +143,7 @@ greeter_parse_config (void) GdmSuspend = ve_config_get_string (config, GDM_KEY_SUSPEND); GdmConfigurator = ve_config_get_string (config, GDM_KEY_CONFIGURATOR); GdmGtkRC = ve_config_get_string (config, GDM_KEY_GTKRC); + GdmServAuthDir = ve_config_get_string (config, GDM_KEY_SERVAUTH); GdmWelcome = ve_config_get_translated_string (config, greeter_Welcome_key); /* A hack! */ @@ -620,6 +623,9 @@ greeter_setup_items (void) NULL); greeter_item_system_setup (); greeter_item_session_setup (); + + /* Setup the custom widgets */ + greeter_item_customlist_setup (); } enum { @@ -1281,7 +1287,7 @@ main (int argc, char *argv[]) GTK_MESSAGE_ERROR, GTK_BUTTONS_OK, s, - /* avoid warning */ "%s", ""); + "%s", (error && error->message) ? error->message : ""); g_free (s); gtk_widget_show_all (dialog); @@ -1294,6 +1300,9 @@ main (int argc, char *argv[]) exit(1); } + if (error) + g_clear_error (&error); + /* Try circles.xml */ if (root == NULL) { @@ -1307,7 +1316,7 @@ main (int argc, char *argv[]) NULL); } - if (greeter_lookup_id ("user-pw-entry") == NULL) + if (root != NULL && greeter_lookup_id ("user-pw-entry") == NULL) { GtkWidget *dialog; diff --git a/gui/greeter/greeter.dtd b/gui/greeter/greeter.dtd index 9f1ed878..77498028 100644 --- a/gui/greeter/greeter.dtd +++ b/gui/greeter/greeter.dtd @@ -4,7 +4,7 @@ font CDATA #IMPLIED tint CDATA #IMPLIED"> <!ELEMENT greeter (item+)> -<!ELEMENT item (pos | normal? | active? | prelight? | children? | show? | text? | fixed? | box?|border?)*> +<!ELEMENT item (pos | normal? | active? | prelight? | children? | show? | text? | fixed? | box? | listitem? | border?)*> <!ELEMENT children (item+)> <!ELEMENT pos EMPTY> <!ELEMENT show EMPTY> @@ -15,12 +15,15 @@ <!ELEMENT stock EMPTY> <!ELEMENT fixed (item+)> <!ELEMENT box (item+)> +<!ELEMENT listitem (text+)> <!-- additional elements--> <!ELEMENT border EMPTY> +<!-- internal id's are one of (user-pw-entry | caps-lock-warning | clock | pam-error | pam-message | pam-prompt | pam-warning | timed-label | language_button | disconnect_button | reboot_button | halt_button | session_button | suspend_button | system_button | config_button | chooser_button | userlist) + but there can be other id's --> <!ATTLIST item type (rect | entry | pixmap | label | svg | rect | list) #REQUIRED - id (user-pw-entry | caps-lock-warning | clock | pam-error | pam-message | pam-prompt | pam-warning | timed-label | language_button | disconnect_button | reboot_button | halt_button | session_button | suspend_button | system_button | config_button | chooser_button | userlist) #IMPLIED + id CDATA #IMPLIED button (true | false) #IMPLIED > <!ATTLIST pos @@ -61,6 +64,9 @@ <!ATTLIST text xml:lang CDATA #IMPLIED > +<!ATTLIST listitem + id CDATA #REQUIRED +> <!-- <border red="0" green="0" blue="10" alpha="255"/>--> diff --git a/gui/greeter/greeter_configuration.h b/gui/greeter/greeter_configuration.h index 5adf1ab7..7c476a77 100644 --- a/gui/greeter/greeter_configuration.h +++ b/gui/greeter/greeter_configuration.h @@ -33,6 +33,7 @@ extern int GdmMinimalUID; extern gboolean GdmAllowRoot; extern gboolean GdmAllowRemoteRoot; extern gchar *GdmWelcome; +extern gchar *GdmServAuthDir; extern gboolean GDM_IS_LOCAL; extern gboolean DOING_GDM_DEVELOPMENT; diff --git a/gui/greeter/greeter_item.c b/gui/greeter/greeter_item.c index a424e9a2..46f6bd9f 100644 --- a/gui/greeter/greeter_item.c +++ b/gui/greeter/greeter_item.c @@ -52,14 +52,35 @@ void greeter_item_info_free (GreeterItemInfo *info) { int i; + GList *list; for (i = 0; i < GREETER_ITEM_STATE_MAX; i++) - if (info->pixbufs[i]) - g_object_unref (G_OBJECT (info->pixbufs[i])); + { + if (info->pixbufs[i]) + g_object_unref (G_OBJECT (info->pixbufs[i])); + if (info->orig_pixbufs[i]) + g_object_unref (G_OBJECT (info->orig_pixbufs[i])); + if (info->files[i]) + g_free (info->files[i]); + if (info->fonts[i]) + pango_font_description_free (info->fonts[i]); + } + + list = info->fixed_children; + info->fixed_children = NULL; + g_list_foreach (list, (GFunc) greeter_item_info_free, NULL); + g_list_free (list); + + list = info->box_children; + info->box_children = NULL; + g_list_foreach (list, (GFunc) greeter_item_info_free, NULL); + g_list_free (list); g_free (info->id); g_free (info->orig_text); g_free (info->show_type); + + memset (info, 0, sizeof (GreeterItemInfo)); g_free (info); } diff --git a/gui/greeter/greeter_item.h b/gui/greeter/greeter_item.h index ba5bf5fa..b42fc8fe 100644 --- a/gui/greeter/greeter_item.h +++ b/gui/greeter/greeter_item.h @@ -4,6 +4,7 @@ #include <libgnomecanvas/libgnomecanvas.h> typedef struct _GreeterItemInfo GreeterItemInfo; +typedef struct _GreeterItemListItem GreeterItemListItem; typedef enum _GreeterItemState GreeterItemState; typedef enum _GreeterItemType GreeterItemType; typedef enum _GreeterItemSizeType GreeterItemSizeType; @@ -90,9 +91,13 @@ struct _GreeterItemInfo { PangoFontDescription *fonts[GREETER_ITEM_STATE_MAX]; char *orig_text; + /* If this is a custom list, then these are the items + to pick from */ + GList *list_items; + /* Container data */ GList *fixed_children; - + GtkOrientation box_orientation; gboolean box_homogeneous; double box_x_padding; @@ -118,6 +123,11 @@ struct _GreeterItemInfo { GtkAllocation allocation; }; +struct _GreeterItemListItem { + char *id; + char *text; +}; + gint greeter_item_event_handler (GnomeCanvasItem *item, GdkEvent *event, gpointer data); diff --git a/gui/greeter/greeter_item_customlist.c b/gui/greeter/greeter_item_customlist.c new file mode 100644 index 00000000..c52ee324 --- /dev/null +++ b/gui/greeter/greeter_item_customlist.c @@ -0,0 +1,122 @@ +#include "config.h" + +#include <gtk/gtk.h> +#include <vicious.h> + +#include "greeter_item.h" +#include "greeter_configuration.h" +#include "greeter_item_customlist.h" +#include "greeter_parser.h" + +enum +{ + GREETER_LIST_TEXT = 0, + GREETER_LIST_ID +}; + +static void +row_selected (GtkTreeSelection *selection, gpointer data) +{ + GtkTreeModel *tm = NULL; + GtkTreeIter iter = {0}; + GreeterItemInfo *item = data; + char *id = NULL; + VeConfig *cfg; + char *file; + + if (DOING_GDM_DEVELOPMENT) + return; + + if (ve_string_empty (item->id)) + return; + + if (gtk_tree_selection_get_selected (selection, &tm, &iter)) + { + gtk_tree_model_get (tm, &iter, GREETER_LIST_ID, + &id, -1); + } + + file = g_strdup_printf ("%s/%s.GreeterInfo", + ve_sure_string (GdmServAuthDir), + ve_sure_string (g_getenv ("DISPLAY"))); + cfg = ve_config_get (file); + g_free (file); + ve_config_set_string (cfg, item->id, ve_sure_string (id)); + ve_config_save (cfg, FALSE); +} + +static void +populate_list (GtkTreeModel *tm, GtkTreeSelection *selection, GList *list_items) +{ + GList *li; + + for (li = list_items; li != NULL; li = li->next) + { + GreeterItemListItem *litem = li->data; + GtkTreeIter iter = {0}; + gtk_list_store_append (GTK_LIST_STORE (tm), &iter); + gtk_list_store_set (GTK_LIST_STORE (tm), &iter, + GREETER_LIST_TEXT, litem->text, + GREETER_LIST_ID, litem->id, + -1); + /* select first item */ + if (li == list_items) + gtk_tree_selection_select_iter (selection, &iter); + } +} + +static void +setup_customlist (GtkWidget *tv, GreeterItemInfo *item) +{ + GtkTreeModel *tm; + GtkTreeViewColumn *column; + GtkTreeSelection *selection; + + gtk_tree_view_set_headers_visible (GTK_TREE_VIEW (tv), + FALSE); + selection = gtk_tree_view_get_selection (GTK_TREE_VIEW (tv)); + gtk_tree_selection_set_mode (selection, GTK_SELECTION_BROWSE); + + g_signal_connect (selection, "changed", + G_CALLBACK (row_selected), + item); + + tm = (GtkTreeModel *)gtk_list_store_new (2, + G_TYPE_STRING, + G_TYPE_STRING); + gtk_tree_view_set_model (GTK_TREE_VIEW (tv), tm); + + column = gtk_tree_view_column_new_with_attributes + ("Choice", + gtk_cell_renderer_text_new (), + "text", GREETER_LIST_TEXT, + NULL); + gtk_tree_view_append_column (GTK_TREE_VIEW (tv), column); + + populate_list (tm, selection, item->list_items); +} + +gboolean +greeter_item_customlist_setup (void) +{ + const GList *custom_items = greeter_custom_items (); + const GList *li; + for (li = custom_items; li != NULL; li = li->next) + { + GreeterItemInfo *info = li->data; + + if (info != NULL && + info->item_type == GREETER_ITEM_TYPE_LIST && + info->item != NULL && + GNOME_IS_CANVAS_WIDGET (info->item)) + { + GtkWidget *sw = GNOME_CANVAS_WIDGET (info->item)->widget; + if (GTK_IS_SCROLLED_WINDOW (sw) && + GTK_IS_TREE_VIEW (GTK_BIN (sw)->child)) + { + setup_customlist (GTK_BIN (sw)->child, info); + } + } + } + return TRUE; +} diff --git a/gui/greeter/greeter_item_customlist.h b/gui/greeter/greeter_item_customlist.h new file mode 100644 index 00000000..4c4fff51 --- /dev/null +++ b/gui/greeter/greeter_item_customlist.h @@ -0,0 +1,8 @@ +#ifndef __GREETER_ITEM_CUSTOMLIST_H__ +#define __GREETER_ITEM_CUSTOMLIST_H__ + +#include "greeter_item.h" + +gboolean greeter_item_customlist_setup (void); + +#endif diff --git a/gui/greeter/greeter_parser.c b/gui/greeter/greeter_parser.c index 9768ce20..9e356fde 100644 --- a/gui/greeter/greeter_parser.c +++ b/gui/greeter/greeter_parser.c @@ -22,6 +22,7 @@ extern GreeterItemInfo *welcome_string_info; static char *file_search_path = NULL; GHashTable *item_hash = NULL; +GList *custom_items = NULL; static gboolean parse_items (xmlNodePtr node, GList **items_out, @@ -1078,6 +1079,7 @@ parse_label (xmlNodePtr node, GREETER_PARSER_ERROR, GREETER_PARSER_ERROR_BAD_SPEC, "A label must specify the text attribute"); + return FALSE; } /* FIXME: evil hack to use internally translated strings */ if (translation_score == 999 && @@ -1110,6 +1112,68 @@ parse_label (xmlNodePtr node, } static gboolean +parse_listitem (xmlNodePtr node, + GreeterItemInfo *info, + GError **error) +{ + xmlNodePtr child; + char *translated_text = NULL; + gint translation_score = 1000; + xmlChar *prop; + GreeterItemListItem *li; + + prop = xmlGetProp (node, "id"); + + if (prop) + { + li = g_new0 (GreeterItemListItem, 1); + li->id = g_strdup (prop); + xmlFree (prop); + } + else + { + g_set_error (error, + GREETER_PARSER_ERROR, + GREETER_PARSER_ERROR_BAD_SPEC, + "Listitem id not specified"); + return FALSE; + } + + child = node->children; + while (child) + { + if (child->type == XML_ELEMENT_NODE && + strcmp (child->name, "text") == 0) + { + if ( ! parse_translated_text (child, &translated_text, &translation_score, error)) + { + g_free (li->id); + g_free (li); + return FALSE; + } + } + + child = child->next; + } + + if (translated_text == NULL) + { + g_free (li->id); + g_free (li); + g_set_error (error, + GREETER_PARSER_ERROR, + GREETER_PARSER_ERROR_BAD_SPEC, + "A list item must specify the text attribute"); + return FALSE; + } + li->text = translated_text; + + info->list_items = g_list_append (info->list_items, li); + + return TRUE; +} + +static gboolean parse_list (xmlNodePtr node, GreeterItemInfo *info, GError **error) @@ -1129,6 +1193,11 @@ parse_list (xmlNodePtr node, if (!parse_show (child, info, error)) return FALSE; } + else if (strcmp (child->name, "listitem") == 0) + { + if ( ! parse_listitem (child, info, error)) + return FALSE; + } else if (strcmp (child->name, "fixed") == 0 || strcmp (child->name, "box") == 0) { @@ -1142,6 +1211,17 @@ parse_list (xmlNodePtr node, child = child->next; } + if (info->list_items != NULL) { + if (strcmp (info->id, "userlist") == 0) { + g_set_error (error, + GREETER_PARSER_ERROR, + GREETER_PARSER_ERROR_BAD_SPEC, + "List of id userlist cannot have custom list items"); + return FALSE; + } + custom_items = g_list_append (custom_items, info); + } + return TRUE; } @@ -1193,6 +1273,8 @@ parse_items (xmlNodePtr node, xmlChar *type; GreeterItemInfo *info; GreeterItemType item_type; + + *items_out = NULL; items = NULL; @@ -1314,6 +1396,7 @@ greeter_parse (const char *file, const char *datadir, GList *items; /* FIXME: EVIL! GLOBAL! */ + g_free (file_search_path); file_search_path = g_strdup (datadir); if (!g_file_test (file, G_FILE_TEST_EXISTS)) @@ -1339,6 +1422,7 @@ greeter_parse (const char *file, const char *datadir, node = xmlDocGetRootElement (doc); if (node == NULL) { + xmlFreeDoc (doc); g_set_error (error, GREETER_PARSER_ERROR, GREETER_PARSER_ERROR_BAD_XML, @@ -1348,6 +1432,7 @@ greeter_parse (const char *file, const char *datadir, if (strcmp (node->name, "greeter") != 0) { + xmlFreeDoc (doc); g_set_error (error, GREETER_PARSER_ERROR, GREETER_PARSER_ERROR_WRONG_TYPE, @@ -1356,21 +1441,34 @@ greeter_parse (const char *file, const char *datadir, } - item_hash = g_hash_table_new_full ((GHashFunc)greeter_info_id_hash, - (GEqualFunc)greeter_info_id_equal, - NULL, - (GDestroyNotify)greeter_item_info_free); + item_hash = g_hash_table_new ((GHashFunc)greeter_info_id_hash, + (GEqualFunc)greeter_info_id_equal); root = greeter_item_info_new (NULL, GREETER_ITEM_TYPE_RECT); res = parse_items (node, &items, root, error); if (!res) { + welcome_string_info = NULL; + + g_hash_table_destroy (item_hash); + item_hash = NULL; + g_list_free (custom_items); + custom_items = NULL; + + g_list_foreach (items, (GFunc) greeter_item_info_free, NULL); + g_list_free (items); + items = NULL; + greeter_item_info_free (root); + xmlFreeDoc (doc); + return NULL; } + xmlFreeDoc (doc); + root->fixed_children = items; root->x = 0; @@ -1387,3 +1485,9 @@ greeter_parse (const char *file, const char *datadir, return root; } + +const GList * +greeter_custom_items (void) +{ + return custom_items; +} diff --git a/gui/greeter/greeter_parser.h b/gui/greeter/greeter_parser.h index cb61ec1f..0ec4a74c 100644 --- a/gui/greeter/greeter_parser.h +++ b/gui/greeter/greeter_parser.h @@ -24,5 +24,6 @@ GreeterItemInfo *greeter_parse (const char *file, GError **error); GreeterItemInfo *greeter_lookup_id (const char *id); +const GList *greeter_custom_items (void); #endif /* __GREETER_PARSER_H__ */ diff --git a/gui/greeter/greeter_system.c b/gui/greeter/greeter_system.c index 1cc00935..46778b59 100644 --- a/gui/greeter/greeter_system.c +++ b/gui/greeter/greeter_system.c @@ -196,8 +196,8 @@ greeter_system_append_system_menu (GtkWidget *menu) G_CALLBACK (query_greeter_halt_handler), NULL); gtk_tooltips_set_tip (tooltips, GTK_WIDGET (w), - _("Shut down your computer so that " - "you may turn it off."), + _("Shut down the system so that " + "you may safely turn off the computer."), NULL); } @@ -393,15 +393,15 @@ greeter_system_handler (GreeterItemInfo *info, return; } - if (gtk_toggle_button_get_active (GTK_TOGGLE_BUTTON (halt_radio))) + if (halt_radio != NULL && gtk_toggle_button_get_active (GTK_TOGGLE_BUTTON (halt_radio))) greeter_halt_handler(); - else if (gtk_toggle_button_get_active (GTK_TOGGLE_BUTTON (reboot_radio))) + else if (reboot_radio != NULL && gtk_toggle_button_get_active (GTK_TOGGLE_BUTTON (reboot_radio))) greeter_reboot_handler (); - else if (gtk_toggle_button_get_active (GTK_TOGGLE_BUTTON (suspend_radio))) + else if (suspend_radio != NULL && gtk_toggle_button_get_active (GTK_TOGGLE_BUTTON (suspend_radio))) greeter_suspend_handler (); - else if (gtk_toggle_button_get_active (GTK_TOGGLE_BUTTON (config_radio))) + else if (config_radio != NULL && gtk_toggle_button_get_active (GTK_TOGGLE_BUTTON (config_radio))) greeter_config_handler (); - else if (gtk_toggle_button_get_active (GTK_TOGGLE_BUTTON (chooser_radio))) + else if (chooser_radio != NULL && gtk_toggle_button_get_active (GTK_TOGGLE_BUTTON (chooser_radio))) greeter_chooser_handler (); gtk_widget_destroy (dialog); diff --git a/omf.make b/omf.make new file mode 100644 index 00000000..2a2b9e7d --- /dev/null +++ b/omf.make @@ -0,0 +1,61 @@ +# +# No modifications of this Makefile should be necessary. +# +# This file contains the build instructions for installing OMF files. It is +# generally called from the makefiles for particular formats of documentation. +# +# Note that you must configure your package with --localstatedir=/var +# so that the scrollkeeper-update command below will update the database +# in the standard scrollkeeper directory. +# +# If it is impossible to configure with --localstatedir=/var, then +# modify the definition of scrollkeeper_localstate_dir so that +# it points to the correct location. Note that you must still use +# $(localstatedir) in this or when people build RPMs it will update +# the real database on their system instead of the one under RPM_BUILD_ROOT. +# +# Note: This make file is not incorporated into xmldocs.make because, in +# general, there will be other documents install besides XML documents +# and the makefiles for these formats should also include this file. +# +# About this file: +# This file was derived from scrollkeeper_example2, a package +# illustrating how to install documentation and OMF files for use with +# ScrollKeeper 0.3.x and 0.4.x. For more information, see: +# http://scrollkeeper.sourceforge.net/ +# Version: 0.1.3 (last updated: March 20, 2002) +# + +omf_dest_dir=$(datadir)/omf/@PACKAGE@ +scrollkeeper_localstate_dir = $(localstatedir)/scrollkeeper + +# At some point, it may be wise to change to something like this: +# scrollkeeper_localstate_dir = @SCROLLKEEPER_STATEDIR@ + +omf: omf_timestamp + +omf_timestamp: $(omffile) + -for file in $(omffile); do \ + scrollkeeper-preinstall $(docdir)/$(docname).xml $(srcdir)/$$file $$file.out; \ + done; \ + touch omf_timestamp + +install-data-hook-omf: + $(mkinstalldirs) $(DESTDIR)$(omf_dest_dir) + for file in $(omffile); do \ + $(INSTALL_DATA) $$file.out $(DESTDIR)$(omf_dest_dir)/$$file; \ + done + -scrollkeeper-update -p $(scrollkeeper_localstate_dir) -o $(DESTDIR)$(omf_dest_dir) + +uninstall-local-omf: + -for file in $(srcdir)/*.omf; do \ + basefile=`basename $$file`; \ + rm -f $(omf_dest_dir)/$$basefile; \ + done + -rmdir $(omf_dest_dir) + -scrollkeeper-update -p $(scrollkeeper_localstate_dir) + +clean-local-omf: + -for file in $(omffile); do \ + rm -f $$file.out; \ + done diff --git a/utils/Makefile.am b/utils/Makefile.am index eeb7c951..f22e4363 100644 --- a/utils/Makefile.am +++ b/utils/Makefile.am @@ -13,7 +13,8 @@ INCLUDES = \ libexec_PROGRAMS = \ @GDMASKPASS@ \ - @GDMOPEN@ + @GDMOPEN@ \ + gdmtranslate # This is not useful anymore # bin_PROGRAMS = \ @@ -24,6 +25,9 @@ EXTRA_PROGRAMS = gdmaskpass gdmopen gdmaskpass_SOURCES = \ gdmaskpass.c +gdmtranslate_SOURCES = \ + gdmtranslate.c + gdmopen_SOURCES = \ gdmopen.c @@ -33,10 +37,13 @@ gdmopen_SOURCES = \ gdmaskpass_LDADD = \ $(INTLLIBS) \ -lpam \ - -lpam_misc + $(EXTRA_GDMASKPASS_LIBS) gdmopen_LDADD = \ $(INTLLIBS) +gdmtranslate_LDADD = \ + $(INTLLIBS) + #gdmmktemp_LDADD = \ # $(INTLLIBS) diff --git a/utils/gdmaskpass.c b/utils/gdmaskpass.c index 09f0eb0e..5270937e 100644 --- a/utils/gdmaskpass.c +++ b/utils/gdmaskpass.c @@ -32,8 +32,8 @@ main (int argc, char *argv[]) } setlocale (LC_ALL, ""); - bindtextdomain (PACKAGE, GNOMELOCALEDIR); - textdomain (PACKAGE); + bindtextdomain (GETTEXT_PACKAGE, GNOMELOCALEDIR); + textdomain (GETTEXT_PACKAGE); for (tries = 3; tries > 0; tries --) { if ((retval = pam_start ("gdm", username, &conv, &pamh)) != PAM_SUCCESS) { diff --git a/utils/gdmtranslate.c b/utils/gdmtranslate.c new file mode 100644 index 00000000..2178a871 --- /dev/null +++ b/utils/gdmtranslate.c @@ -0,0 +1,34 @@ +#include "config.h" +#include <libgnome/libgnome.h> +#include <stdio.h> +#include <locale.h> +#include <string.h> + +int +main (int argc, char *argv[]) +{ + char *string; + gboolean is_utf8 = FALSE; + + if (argc == 3 && + strcmp (argv[1], "--utf8") == 0) { + string = argv[2]; + is_utf8 = TRUE; + } else if (argc == 2) { + string = argv[1]; + is_utf8 = FALSE; + } else { + fprintf (stderr, "usage: gdmtranslate [--utf8] <string to translate>\n"); + return 0; + } + + setlocale (LC_ALL, ""); + bindtextdomain (GETTEXT_PACKAGE, GNOMELOCALEDIR); + if (is_utf8) + bind_textdomain_codeset (GETTEXT_PACKAGE, "UTF-8"); + textdomain (GETTEXT_PACKAGE); + + printf ("%s\n", _(string)); + + return 0; +} diff --git a/xmldocs.make b/xmldocs.make new file mode 100644 index 00000000..0bc35963 --- /dev/null +++ b/xmldocs.make @@ -0,0 +1,95 @@ +# +# No modifications of this Makefile should be necessary. +# +# To use this template: +# 1) Define: figdir, docname, lang, omffile, and entities in +# your Makefile.am file for each document directory, +# although figdir, omffile, and entities may be empty +# 2) Make sure the Makefile in (1) also includes +# "include $(top_srcdir)/xmldocs.make" and +# "dist-hook: app-dist-hook". +# 3) Optionally define 'entities' to hold xml entities which +# you would also like installed +# 4) Figures must go under $(figdir)/ and be in PNG format +# 5) You should only have one document per directory +# 6) Note that the figure directory, $(figdir)/, should not have its +# own Makefile since this Makefile installs those figures. +# +# example Makefile.am: +# figdir = figures +# docname = scrollkeeper-manual +# lang = C +# omffile=scrollkeeper-manual-C.omf +# entities = fdl.xml +# include $(top_srcdir)/xmldocs.make +# dist-hook: app-dist-hook +# +# About this file: +# This file was taken from scrollkeeper_example2, a package illustrating +# how to install documentation and OMF files for use with ScrollKeeper +# 0.3.x and 0.4.x. For more information, see: +# http://scrollkeeper.sourceforge.net/ +# Version: 0.1.2 (last updated: March 20, 2002) +# + + +# ********** Begin of section some packagers may need to modify ********** +# This variable (docdir) specifies where the documents should be installed. +# This default value should work for most packages. +docdir = $(datadir)/gnome/help/$(docname)/$(lang) + +# ********** You should not have to edit below this line ********** +xml_files = $(entities) $(docname).xml + +EXTRA_DIST = $(xml_files) $(omffile) +CLEANFILES = omf_timestamp + +include $(top_srcdir)/omf.make + +all: omf + +$(docname).xml: $(entities) + -ourdir=`pwd`; \ + cd $(srcdir); \ + cp $(entities) $$ourdir + +app-dist-hook: + if test "$(figdir)"; then \ + $(mkinstalldirs) $(distdir)/$(figdir); \ + for file in $(srcdir)/$(figdir)/*.png; do \ + basefile=`echo $$file | sed -e 's,^.*/,,'`; \ + $(INSTALL_DATA) $$file $(distdir)/$(figdir)/$$basefile; \ + done \ + fi + +install-data-local: omf + $(mkinstalldirs) $(DESTDIR)$(docdir) + for file in $(xml_files); do \ + cp $(srcdir)/$$file $(DESTDIR)$(docdir); \ + done + if test "$(figdir)"; then \ + $(mkinstalldirs) $(DESTDIR)$(docdir)/$(figdir); \ + for file in $(srcdir)/$(figdir)/*.png; do \ + basefile=`echo $$file | sed -e 's,^.*/,,'`; \ + $(INSTALL_DATA) $$file $(DESTDIR)$(docdir)/$(figdir)/$$basefile; \ + done \ + fi + +install-data-hook: install-data-hook-omf + +uninstall-local: uninstall-local-doc uninstall-local-omf + +uninstall-local-doc: + -if test "$(figdir)"; then \ + for file in $(srcdir)/$(figdir)/*.png; do \ + basefile=`echo $$file | sed -e 's,^.*/,,'`; \ + rm -f $(docdir)/$(figdir)/$$basefile; \ + done; \ + rmdir $(DESTDIR)$(docdir)/$(figdir); \ + fi + -for file in $(xml_files); do \ + rm -f $(DESTDIR)$(docdir)/$$file; \ + done + -rmdir $(DESTDIR)$(docdir) + +clean-local: clean-local-omf |
