Brian Cameron wrote: >>> - If the /var/cache/gdm/user-$uid/dmrc file does not exist, then >>> GDM will log the user into the default session/language or whichever >>> ones they selected in the GUI. Then it will save the dmrc file to >>> the cache with the default settings. On next login, the defaults >>> will be read from the cache and not the user's $HOME directory. >> >> The cache should also be updated at logout time, if at all possible. >> (But the system component doing a logout-time update wouldn't >> necessarily be part of GDM.) > > A logout update is not necessary for caching this file since the choices > can only be selected in the login GUI before authenticating. If the > values change, you know they have changed before authentication.
If $HOME is shared across systems then my ~/.dmrc can be changed by a login through a GDM running on some other machine. That would mean that the cache on *this* machine would become stale. That's not necessarily a bad thing but it could be confusing to users. What does GDM do if the session type specified in my ~/.dmrc is not available on this system? I hope it proceeds as though no session-type entry had been found. BTW, dtlogin avoids the pre-authentication $HOME access issue by not translating a "follow user's previous session selection" choice to a concrete session type until the desktop is actually being launched, long after authentication has succeeded and the user's session credentials have been established. Mike. -- mike.oliver at sun.com
