Hi again,
Point 3 is likely for upstream?
The issue here is that you cant stop/start the vmblock filesystem as
long as anyone is using it. Supposedly you would send a signal to
the
user daemons, telling them to give up any references to it - but
its
not handled and instead the user daemon terminates.
what I forgot here: upstream ships a pam config, which doesn't find its
way into the package into the package yet. I have to investigate what
else is missing. I think I'll do everything form scratch, but I just
didn't have the time to do so since I took over the maintenance.
for /etc/pam.d/vmtoolsd:
#%PAM-1.0
auth sufficient pam_unix2.so nullok
auth sufficient pam_unix.so shadow nullok
auth required pam_unix_auth.so shadow nullok
account sufficient pam_unix2.so
account sufficient pam_unix.so
account required pam_unix_acct.so
Could you give that a try (I guess it needs some modifications),
but it might fix some issues - not sure though.
Thanks,
Bernd
--
Bernd Zeimetz Debian GNU/Linux Developer
http://bzed.de http://www.debian.org
GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
