В Wed, 22 Oct 2014 16:54:45 +0200
Reindl Harald h.rei...@thelounge.net пишет:
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;
Am 22.10.2014 um 18:31 schrieb Andrei Borzenkov:
В Wed, 22 Oct 2014 16:54:45 +0200
Reindl Harald h.rei...@thelounge.net пишет:
[root@sftp:~]$ kill 29657
[root@sftp:~]$ cat messages
Oct 22 16:51:48 sftp systemd: Failed at step CHDIR spawning
/usr/bin/kill: No such file or directory
This
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
as opposed to KillMode=mixed. I think this is why I haven't been able
to reproduce this on my Fedora 20 box recently. The
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
Hi all,
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
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
