On Tue, 16.12.14 08:45, David Herrmann (dh.herrm...@gmail.com) wrote:
Hi
On Mon, Dec 15, 2014 at 9:20 PM, Dan Williams d...@redhat.com wrote:
On Mon, 2014-12-15 at 20:40 +0300, Andrei Borzenkov wrote:
systemd tries to launch logind service which now waits for services it
is ordered
В Mon, 15 Dec 2014 14:20:45 -0600
Dan Williams d...@redhat.com пишет:
On Mon, 2014-12-15 at 20:40 +0300, Andrei Borzenkov wrote:
В Mon, 15 Dec 2014 11:34:17 -0600
Dan Williams d...@redhat.com пишет:
On Mon, 2014-12-15 at 16:11 +0100, Lennart Poettering wrote:
On Sat, 13.12.14
On Tue, 2014-12-16 at 08:45 +0100, David Herrmann wrote:
Hi
On Mon, Dec 15, 2014 at 9:20 PM, Dan Williams d...@redhat.com wrote:
On Mon, 2014-12-15 at 20:40 +0300, Andrei Borzenkov wrote:
systemd tries to launch logind service which now waits for services it
is ordered After and
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
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 actually
В Mon, 15 Dec 2014 11:34:17 -0600
Dan Williams d...@redhat.com пишет:
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
On Mon, 2014-12-15 at 20:40 +0300, Andrei Borzenkov wrote:
В Mon, 15 Dec 2014 11:34:17 -0600
Dan Williams d...@redhat.com пишет:
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
Hi
On Mon, Dec 15, 2014 at 9:20 PM, Dan Williams d...@redhat.com wrote:
On Mon, 2014-12-15 at 20:40 +0300, Andrei Borzenkov wrote:
systemd tries to launch logind service which now waits for services it
is ordered After and eventually times out.
NM patch filed for review by NM dev team:
NetworkManager sets logind inhibitor lock to monitor for suspend
events. So it implicitly requires logind to be present when NM starts.
logind is ordered after nss-user-lookup.target. If we have remote user
database, it means that logind depends on network to be up and running.
If network is
