Summary: | sys-auth/pam_mount causes error in app-admin/sudo: HXproc_run_async: pmvarrun: No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ihar Hrachyshka <ihar.hrachyshka> |
Component: | [OLD] Core system | Assignee: | Hanno Böck <hanno> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | base-system, gef.kornflakes, hkmaly, mephinet, mlspamcb, pam-bugs+disabled, rdwald |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ihar Hrachyshka
2010-08-03 09:25:24 UTC
Hmm I don't think you should be using pam_mount with system-auth but rather with system-login. Semantics do change a lot. Thanks, Diego, this helps. of course it's not a complete fix, as it shouldn't be printing that repeatedly... I wonder why it doesn't actually hardcode the full path in the module... and why it installs in /usr/sbin at all, it seems it should be in /usr/libexec to me. But Hanno will know better :) Actually, the 'fix' didn't work - it worked for me just because I was already logged in so there was no need to mount home partition. I didn't manage to setup pam_mount module to be loaded by PAM when using system-login so I reverted back to system-auth file and it works again. Diego, could you suggest documentation on how to set pam_mount up with system-login file? Currently it's beyond my understanding. I'm running into the same bug with sudo-1.7.3 and pam_mount...what configuration files do you guys want? I really don't understand, 1.7.3 shows no change in PATH handling. But whatever the problem, I can't see why pam_mount should rely on PATH being set at all. Hanno can you make it hardcode the path during build? I already receive two message for chagne in this bug, no more please. The solution for me was: modify the <pmvarrun /> entry to point to /usr/sbin/pmvarrun by default it is appearantly searchfor in the users path (and an ordinary users doesn't have /usr/sbin in its path). Also note that the upgrade of pam_mount wipes the pam_mount.conf.xml not nice. Luckily I had a backup of it. This also isn't sudo problem but a pam_mount problem (In reply to comment #8) > The solution for me was: > modify the <pmvarrun /> entry to point to /usr/sbin/pmvarrun > by default it is appearantly searchfor in the users path (and an ordinary users > doesn't have /usr/sbin in its path). I can confirm the following line in pam_mount.conf.xml helps for non-root logins: <pmvarrun>/usr/sbin/pmvarrun -u %(USER)</pmvarrun> I've now changed pam_mount to install pmvarrun to bin instead of sbin. This should fix this. I've also sent this upstream, let's see if he likes this solution or if we find another one. |