On Tue, 2014-12-16 at 08:45 +0100, David Herrmann wrote: > Hi > > On Mon, Dec 15, 2014 at 9:20 PM, Dan Williams <[email protected]> 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: > > > > https://bugzilla.gnome.org/show_bug.cgi?id=741572 > > Thanks a lot!
Update: the patch has been reviewed and pushed to NM git master (will eventually be 1.2), nm-1-0, and nm-0-9-10 branches. Dan > > Also, I don't think logind should fail if there is no network; no reason > > for it to crash and burn just because everything isn't quite ready when > > it starts. I presume it's got capability to deal with sporadic network > > outages, and that's not really different than waiting for networking to > > show up soon after it starts. But not my department... > > When a user loggs in, we resolve the name to UID. As the initial > logind binary was only used for login management, it was reasonable to > avoid starting up before the nss-user-lookup is initialized. Now that > systemd-logind provides other independent APIs, it might be ok to drop > that requirement again. > If the nss user lookup is not ready at the time someone logs in, we > will print a warning and skip tracking that session. Sounds fine to > me, but Lennart might have more comments. > > Thanks > David _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
