Am 22.10.2014 um 16:49 schrieb Chris Bell:
I'm running into an annoying issue. I use systemd 216 on an Arch box, and systemd 208 on a Fedora box; the issue exists on both. Logins are handled through getty; there is no desktop manager involved. Occasionally, on shutdown, I get a 90 second hold while waiting for a 'Stop Job for User 1000'. Logging out before shutdown reduces, but does not eliminate, the occurrence.The issue is documented in far more detail at https://bugs.freedesktop.org/show_bug.cgi?id=70593 ; I'm the Chris in the comments (starting with #15). I was led here for assistance with the following questions related to this issue: What, exactly, is this stop job? What's it waiting for? Why 90 seconds? Can this duration be changed? Where should I start bughunting here?
there are more rough edges in that contextthat 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
[root@sftp:~]$ ps aux | grep 29657**** 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
[root@sftp:~]$ kill 29657 [root@sftp:~]$ cat messagesOct 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
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.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
