On Mon, Jan 23, 2012 at 16:05, Mike Kazantsev wrote:
> On Mon, 23 Jan 2012 12:22:46 -0200
> Gustavo Sverzut Barbieri wrote:
>
>> On Mon, Jan 23, 2012 at 11:51 AM, Mike Kazantsev
>> wrote:
>> > On Mon, 23 Jan 2012 09:16:52 +0100
>> > Christian Hesse wrote:
>> >
>> >> Hello everybody,
>> >>
>> >
On Mon, 23 Jan 2012 12:22:46 -0200
Gustavo Sverzut Barbieri wrote:
> On Mon, Jan 23, 2012 at 11:51 AM, Mike Kazantsev wrote:
> > On Mon, 23 Jan 2012 09:16:52 +0100
> > Christian Hesse wrote:
> >
> >> Hello everybody,
> >>
> >> I think systemd caring about session is a great idea and I added
> >
On Mon, Jan 23, 2012 at 11:51 AM, Mike Kazantsev wrote:
> On Mon, 23 Jan 2012 09:16:52 +0100
> Christian Hesse wrote:
>
>> Hello everybody,
>>
>> I think systemd caring about session is a great idea and I added
>> "kill-session-processes=1" to systemd's configuration in pam files.
>> However this
On Mon, 23 Jan 2012 19:51:52 +0600
Mike Kazantsev wrote:
> On Mon, 23 Jan 2012 09:16:52 +0100
> Christian Hesse wrote:
>
> > Hello everybody,
> >
> > I think systemd caring about session is a great idea and I added
> > "kill-session-processes=1" to systemd's configuration in pam files.
> > How
On Mon, 23 Jan 2012 09:16:52 +0100
Christian Hesse wrote:
> Hello everybody,
>
> I think systemd caring about session is a great idea and I added
> "kill-session-processes=1" to systemd's configuration in pam files.
> However this brings some problems. (Two for me to be precisely.)
>
> First on
Hello everybody,
I think systemd caring about session is a great idea and I added
"kill-session-processes=1" to systemd's configuration in pam files.
However this brings some problems. (Two for me to be precisely.)
First one was tmux. Detaching a tmux session and logging off used to kill the
tmux
