Am 22.10.2014 um 18:31 schrieb Andrei Borzenkov:
В Wed, 22 Oct 2014 16:54:45 +0200
Reindl Harald пишет:
[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 sounds like exactly the sa
В Wed, 22 Oct 2014 16:54:45 +0200
Reindl Harald пишет:
>
> 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
On Thu, 23.10.14 11:38, Chris Bell (cwb...@mail.usf.edu) wrote:
> 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
Not sure I grok this? Colin?
> as opposed to KillMod
Chris Bell wrote on 23/10/14 16:38:
> 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.
FWIW, I think KillMode=mixed is the preferred o
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 machin
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 discus
On Wed, Oct 22, 2014 at 10:49 AM, Chris Bell wrote:
> Why 90 seconds? Can this duration be changed?
Could I accomplish this with the `JobTimeoutSec' systemd parameter in
the `user@.service' unit file? I can't seem to force my system to get
stuck on a stop job at the moment to test it. Would chang
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 wh
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