Mike: >>>> - 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.
If we move the dmrc file to /var/cache, then this issue would go away. So I think that is a good idea. > 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. It uses the system default if the choice in your $HOME/.dmrc file is not available. Brian
