Lennart Poettering on Sat, 11 Feb 2012 00:59:47
+0100:
> On Fri, 10.02.12 22:34, Christian Hesse (l...@eworm.de) wrote:
>
> > > > > Well, strace the PAM client which invokes the PAM session hooks and
> > > > > figure out where exactly the fifo is closed and by what piece of
> > > > > code. The FI
On Fri, 10.02.12 22:34, Christian Hesse (l...@eworm.de) wrote:
> > > > Well, strace the PAM client which invokes the PAM session hooks and
> > > > figure out where exactly the fifo is closed and by what piece of
> > > > code. The FIFO fd is received via a dbus reply (which you'll see as a
> > > >
Cristian RodrÃguez on Fri, 10 Feb 2012 18:05:42
-0300:
> On 09/02/12 14:50, Christian Hesse wrote:
> > Hello everybody,
> >
> > starting with systemd v40 I have problems with graphical login managers
> > (tested with lightdm and slim on Arch).
> > After successful user authentication the login man
Lennart Poettering on Fri, 10 Feb 2012 21:02:03
+0100:
> On Fri, 10.02.12 09:48, Christian Hesse (l...@eworm.de) wrote:
>
> >
> > Lennart Poettering on Thu, 9 Feb 2012 22:29:38
> > +0100:
> > > On Thu, 09.02.12 20:57, Christian Hesse (l...@eworm.de) wrote:
> > > > > systemd-logind tracks open
On 09/02/12 14:50, Christian Hesse wrote:
Hello everybody,
starting with systemd v40 I have problems with graphical login managers
(tested with lightdm and slim on Arch).
After successful user authentication the login manager is killed by
systemd-logind with SIGTERM. I think this is because of t
On Fri, 10.02.12 09:48, Christian Hesse (l...@eworm.de) wrote:
>
> Lennart Poettering on Thu, 9 Feb 2012 22:29:38 +0100:
> > On Thu, 09.02.12 20:57, Christian Hesse (l...@eworm.de) wrote:
> > > > systemd-logind tracks open sessions by keeping open a FIFO fd to the PAM
> > > > session client. Wh
Lennart Poettering on Thu, 9 Feb 2012 22:29:38 +0100:
> On Thu, 09.02.12 20:57, Christian Hesse (l...@eworm.de) wrote:
> > > systemd-logind tracks open sessions by keeping open a FIFO fd to the PAM
> > > session client. When the session client dies then systemd will see that
> > > as EOF. Now, if
On Thu, 09.02.12 20:57, Christian Hesse (l...@eworm.de) wrote:
> > Yes, there have been similar reports.
>
> Glad to hear I am not the only one... Could not find any reports so
> far.
There were a couple on #systemd.
> > systemd-logind tracks open sessions by keeping open a FIFO fd to the PAM
>
Lennart Poettering on Thu, 9 Feb 2012 19:38:39 +0100:
> On Thu, 09.02.12 18:50, Christian Hesse (l...@eworm.de) wrote:
>
> > Hello everybody,
> >
> > starting with systemd v40 I have problems with graphical login managers
> > (tested with lightdm and slim on Arch).
> > After successful user auth
On Thu, 09.02.12 18:50, Christian Hesse (l...@eworm.de) wrote:
> Hello everybody,
>
> starting with systemd v40 I have problems with graphical login managers
> (tested with lightdm and slim on Arch).
> After successful user authentication the login manager is killed by
> systemd-logind with SIGTE
Hello everybody,
starting with systemd v40 I have problems with graphical login managers
(tested with lightdm and slim on Arch).
After successful user authentication the login manager is killed by
systemd-logind with SIGTERM. I think this is because of the changes in commit
"logind: if we have to
11 matches
Mail list logo
