Joerg: >> - /usr/bin/gdmdynamic [--add=DISPLAY | --delete=DISPLAY | --list ] > > This still allows specifying the X server to start when adding a > display, doesn't it?
Yes, although this is not specified on the gdmdynamic command any longer. Instead this is specified in the ConsoleKit configuration. The /usr/bin/gdmdynamic script passes ck-seat-tool the --display-type=Sunray argument, which specifies the Xserver to use. >> - /usr/lib/gdm-user-switch-applet >> >> The Fast-User-Switch-Applet. When VT is enabled, this applet allows >> users to quickly switch to a login screen on a separate VT. The >> username value will be pre-filled if the user has selected a user in >> the applet, so the user only needs to enter the password. Therefore, >> this feature may not be useful with some PAM stacks. >> > > Does gdm-user-switch-applet use the same PAM stack as regular gdm login? Yes, the Fast User Switch applet just tells GDM to start up a new VT session and passes along the userid that the user has picked. Then GDM starts the normal PAM session passing in PAM_USER. > PAM clients that supply a user to pam_start(3PAM) are quite common. Are > you thinking of specific PAM stacks that would fail in this scenario? I simply meant that the Fast User Switch applet assumes that the PAM stack will work with a supplied username. Not all PAM stacks will work with the Fast User Switch applet. For example, if you configured a system to only work with a fingerprint scanner, the Fast User Switch applet would not work with that since the username is associated with the fingerprint and not something that is supplied. Brian
