I'm primarily a
User Developer Sysadmin A mixture Something else entirely .. ( 373 votes ~ 6 comments )
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
#2 Re: GNOME and libpam-mount Posted by dkg (166.84.xx.xx) on Sun 11 May 2008 at 23:10 Unmounting on logout is the problem i plan to deal with after i get a handle on the sqlite-over-cifs business. For a simple terminal session (from a getty on VT's 1 through 6 in the normal config), unmounting on logout works reliably. But an X11 login -- or rather, i should say, a GNOME login -- fails far more often than not. FWICT, this is because many of the GNOME daemons deliberately detach and orphan themselves from the session. Since they're children of PID 1, they can't be easily cleaned up or signaled by session shutdown. So the session closes, and things like tracker, gconf-d, and bonobo-activation-server persist, if only for a minute or two. Well, that minute is long enough to make it so that pam_mount can't unmount the home directory. If you've got an encrypted home directory, that's a security concern. If you're mounting a network-offered directory with multiple home directories on it (but only mounting one at a time, depending on who's logged in at the console), you've got other problems, because the previous user's permissions will be set on the mountpoint when the next user tries to log in.
But an X11 login -- or rather, i should say, a GNOME login -- fails far more often than not. FWICT, this is because many of the GNOME daemons deliberately detach and orphan themselves from the session. Since they're children of PID 1, they can't be easily cleaned up or signaled by session shutdown. So the session closes, and things like tracker, gconf-d, and bonobo-activation-server persist, if only for a minute or two.
Well, that minute is long enough to make it so that pam_mount can't unmount the home directory. If you've got an encrypted home directory, that's a security concern. If you're mounting a network-offered directory with multiple home directories on it (but only mounting one at a time, depending on who's logged in at the console), you've got other problems, because the previous user's permissions will be set on the mountpoint when the next user tries to log in.
Posting Format:
Inappropriate comments will be removed.
Some help on entry formatting is available
Username:
Password:
[ Advanced Login ]
Register Account
