Re: [systemd-devel] Stop Job for User Manager

[Reindl Harald]

Am 23.10.2014 um 17:38 schrieb Chris Bell:

It looks like Fedora recently implemented changes in the user@.service
unit file to address this issue. They use:

ExecStop=/bin/kill -TERM ${MAINPID}
KillSignal=SIGCONT

fine, but it don't help really
i have exactly that setting on F20 and some machines just hang



[root@sftp:~]$ ps aux | grep 29657


[root@sftp:~]$ kill 29657

[root@sftp:~]$ cat messages

Oct 22 16:51:48 sftp systemd: Failed to start Exit the Session.
Oct 22 16:51:48 sftp systemd: Dependency failed for Exit the Session.
Oct 22 16:51:48 sftp systemd:
Oct 22 16:51:48 sftp systemd: Unit systemd-exit.service entered failed state

that below is a system-session triggered by SSHD with openssh-chroot in combination with pam-mysql - obviously the user-manager inherits the sshd-chroot and so can't call the kill command **** 29657 0.0 0.4 46580 4288 ? Ss Okt17 0:00 /usr/lib/systemd/systemd --user root 31532 0.0 0.2 112684 2160 pts/0 S<+ 16:51 0:00 /usr/bin/grep --color 29657 Oct 22 16:51:48 sftp systemd: Failed at step CHDIR spawning /usr/bin/kill: No such file or directory Oct 22 16:51:48 sftp systemd: systemd-exit.service: main process exited, code=exited, status=200/CHDIR

signature.asc
Description: OpenPGP digital signature

_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel