Re: [systemd-devel] KillUserProcesses timeout

2015-04-27 Thread Mikhail Morfikov
This is the log when my system works as usual: (loginctl session-status) 1 - morfik (1000) Since: Sun 2015-04-26 23:19:01 CEST; 18h ago Leader: 1720 (lightdm) Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user State: o

Re: [systemd-devel] KillUserProcesses timeout

2015-04-27 Thread Lennart Poettering
On Fri, 24.04.15 20:54, Mikhail Morfikov (mmorfi...@gmail.com) wrote: > On Fri, 24 Apr 2015 19:04:53 +0200 > Lennart Poettering wrote: > > > On Tue, 27.01.15 04:28, Mikhail Morfikov (mmorfi...@gmail.com) wrote: > > > > Sorry for the really late reply, still trying to work through piles of > > m

Re: [systemd-devel] KillUserProcesses timeout

2015-04-24 Thread Mikhail Morfikov
On Fri, 24 Apr 2015 19:04:53 +0200 Lennart Poettering wrote: > On Tue, 27.01.15 04:28, Mikhail Morfikov (mmorfi...@gmail.com) wrote: > > Sorry for the really late reply, still trying to work through piles of > mail. > > > > > Hmm, not sure I follow. > > > > > > > It only happens if I'm logge

Re: [systemd-devel] KillUserProcesses timeout

2015-04-24 Thread Lennart Poettering
On Tue, 27.01.15 04:28, Mikhail Morfikov (mmorfi...@gmail.com) wrote: Sorry for the really late reply, still trying to work through piles of mail. > > > Hmm, not sure I follow. > > > > It only happens if I'm logged in as root in tmux. > > > The session is shown as closing, that's good. Can y

Re: [systemd-devel] KillUserProcesses timeout

2015-01-26 Thread Mikhail Morfikov
> Hmm, not sure I follow. > It only happens if I'm logged in as root in tmux. > The session is shown as closing, that's good. Can you check what > "systemctl status" reports on the scope unit if this hang happens? > > Lennart > I'm not sure if I did the right thing, but there it is. Afte

Re: [systemd-devel] KillUserProcesses timeout

2015-01-26 Thread Lennart Poettering
On Tue, 27.01.15 02:12, Mikhail Morfikov (mmorfi...@gmail.com) wrote: > > > Normally, the SIGTERM should be delivered instantly on logout from > > logind. Unless the PAM session end hook wasn't called or so. > > > > If you log in as root, and then reproduce the 20s wait for another > > user what

Re: [systemd-devel] KillUserProcesses timeout

2015-01-26 Thread Mikhail Morfikov
> Normally, the SIGTERM should be delivered instantly on logout from > logind. Unless the PAM session end hook wasn't called or so. > > If you log in as root, and then reproduce the 20s wait for another > user what does "loginctl session-status" and "loginctl user-status" > say about the session/

Re: [systemd-devel] KillUserProcesses timeout

2015-01-26 Thread Lennart Poettering
On Tue, 27.01.15 01:00, Mikhail Morfikov (mmorfi...@gmail.com) wrote: > > Sorry, but I cannot parse this. Do you want a delay because when > > logging out and back in you want to be able to reuse your old > > gpg-agent? Or what precisely is the current behaviour and what do you > > want it to be i

Re: [systemd-devel] KillUserProcesses timeout

2015-01-26 Thread Mikhail Morfikov
> Sorry, but I cannot parse this. Do you want a delay because when > logging out and back in you want to be able to reuse your old > gpg-agent? Or what precisely is the current behaviour and what do you > want it to be instead? > > Lennart > No, I just want to speed it up. Now I have to wait abou

Re: [systemd-devel] KillUserProcesses timeout

2015-01-26 Thread Lennart Poettering
On Mon, 26.01.15 20:17, Mikhail Morfikov (mmorfi...@gmail.com) wrote: > I'm using standalone Openbox and when I log out by killing Xserver > (ctrl+alt+backspace), some processes stay alive even though the user > logged out completely. I know there's a KillUserProcesses option in > the /etc/systemd