You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the weblog GNOME and libpam-mount

#8 Re: GNOME and libpam-mount Posted by dkg (216.254.xx.xx) on Mon 12 May 2008 at 19:23 I agree that this is a reasonable interpretation of where to "fix" this piece of the problem. If you break out common-pammount into two files, though, each one would only have a single line of configuration. So it might just be better to remove /etc/pam.d/common-pammount altogether, and to clean up the documentation to explain exactly what to add (and where to add it) for the most common use cases. (e.g. in common-auth and common-session for the "work with everything" case, and how to specifically enable it for select PAM services). I'll file a bug against libpam-mount about its documentation and default config later today. Approaching this from the other angle, is there anything that could be done to make the GNOME side of things more robust in the face of a not-yet-mounted homedir during PAM session initiation? For example, should i be filing a bug against libpam-gnome-keyring for kicking off gconfd-2 when $HOME isn't present? or against libgconf2-4 for gconfd-2's inability to cope with a $HOME that is created or mounted after gconfd-2 is started? Or is there some other way GNOME could address this?

Inappropriate comments will be removed.

Username:

Password:

[ Advanced Login ]

Register Account