В Mon, 15 Dec 2014 14:20:45 -0600
Dan Williams пишет:
> On Mon, 2014-12-15 at 20:40 +0300, Andrei Borzenkov wrote:
> > В Mon, 15 Dec 2014 11:34:17 -0600
> > Dan Williams пишет:
> >
> > >
> > > On Mon, 2014-12-15 at 16:11 +0100, Lennart Poettering wrote:
> > > > On Sat, 13.12.14 10:09, Andrei B
On Mon, 2014-12-15 at 20:40 +0300, Andrei Borzenkov wrote:
> В Mon, 15 Dec 2014 11:34:17 -0600
> Dan Williams пишет:
>
> >
> > On Mon, 2014-12-15 at 16:11 +0100, Lennart Poettering wrote:
> > > On Sat, 13.12.14 10:09, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> > >
> > > > NetworkManager se
В Mon, 15 Dec 2014 11:34:17 -0600
Dan Williams пишет:
>
> On Mon, 2014-12-15 at 16:11 +0100, Lennart Poettering wrote:
> > On Sat, 13.12.14 10:09, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> >
> > > NetworkManager sets logind inhibitor lock to monitor for suspend
> > > events. So it implici
On Sat, 13.12.14 10:09, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> NetworkManager sets logind inhibitor lock to monitor for suspend
> events. So it implicitly requires logind to be present when NM
> starts.
Any idea what it needs the inhibitor for?
> logind is ordered after nss-user-lookup.
On Mon, 2014-12-15 at 16:11 +0100, Lennart Poettering wrote:
> On Sat, 13.12.14 10:09, Andrei Borzenkov (arvidj...@gmail.com) wrote:
>
> > NetworkManager sets logind inhibitor lock to monitor for suspend
> > events. So it implicitly requires logind to be present when NM
> > starts.
NM doesn't ac
