Re: umount NFS problem

[Lennart Poettering <lennart@xxxxxxxxxxxxxx>]

On Fr, 05.04.19 11:53, Harald Dunkel (harald.dunkel@xxxxxxxxx) wrote:

> Hi Lennart,
>
> On 4/5/19 10:28 AM, Lennart Poettering wrote:
> >
> > For some reason a number of X session processes stick around to the
> > very end and thus keep your /home busy.
> >
> > [82021.052357] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
> > [82021.101976] systemd-shutdown[1]: Sending SIGKILL to PID 2513 (gpg-agent).
> > [82021.130507] systemd-shutdown[1]: Sending SIGKILL to PID 2886 (xstartup).
> > [82021.158510] systemd-shutdown[1]: Sending SIGKILL to PID 2896 (xstartup).
> > [82021.186052] systemd-shutdown[1]: Sending SIGKILL to PID 2959 (xterm).
> > [82021.213129] systemd-shutdown[1]: Sending SIGKILL to PID 2960 (xterm).
> > [82021.239971] systemd-shutdown[1]: Sending SIGKILL to PID 2961 (xterm).
> > [82021.266285] systemd-shutdown[1]: Sending SIGKILL to PID 2966 (bash).
> > [82021.292234] systemd-shutdown[1]: Sending SIGKILL to PID 2967 (bash).
> > [82021.318061] systemd-shutdown[1]: Sending SIGKILL to PID 9146 (utempter).
> > [82021.343331] systemd-shutdown[1]: Sending SIGKILL to PID 9147 (utempter).
> >
> > The question is how though. How do you start your X session? gdm?
> > startx from the console?
> >
>
> This is a VNC session, started via crontab @reboot.

IIRC debian/ubuntu do not have pam-systemd in their PAM configuration
for cron, which means these services are not tracked by
logind/systemd, and hence only killed when crond likes to do that.

It's a configuration bug in debian/ubuntu.

Lennart

--
Lennart Poettering, Berlin
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel