Well, either case is embarrasing. If the network is up after the user logins, that's ridiculous, even Windows start his services before the login screen. If NM, thus the network, is *slow* to start, that's worse! Isn't supposed systemd would speed up the boot process?
This is worse than the "kill user's background processes after logout" case. Thanks for sharing. On Fri, Jul 15, 2016 at 6:22 PM, Simon Hobson <li...@thehobsons.co.uk> wrote: > > On 15 Jul 2016, at 18:10, Emiliano Marini <emilianomarin...@gmail.com> > wrote: > > > Are you serious network isn't started before user login? This is... You > can't be serious. Link please? > > Ah, I'd mis-rembered the thread. The frontend was consistently not > starting. > > http://lists.mythtv.org/pipermail/mythtv-users/2016-July/387810.html > > > For me on Mythbuntu 16.04 it looks like the network is slow to start > because > > the network interface details are not set by the NetworkManager software > > until the user-login is complete. > > Now whether that's because it doesn't start until user login, or because > it's been set to auto-login at start and the network manager is just slow I > don't know. But it's fail (by some definition of fail) that it's even > starting login before the network is up (by whatever definition of up you > use). > > _______________________________________________ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng >
_______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
