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
On 15 Jul 2016, at 18:10, Emiliano Marini 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/387
Are you serious network isn't started before user login? This is... You
can't be serious. Link please?
On Wed, Jul 13, 2016 at 6:59 PM, Simon Hobson
wrote:
> Jaromil wrote:
>
> >> Hi, over on the Samba mailing list, somebody asked what
> '--with-systemd' was
> >> for. It has now degenerated int
On Wed, 13 Jul 2016 22:59:40 +0100
Simon Hobson wrote:
> Jaromil wrote:
> There's also been a short thread on the MythTV mailing list about how
> to get the MythTV Frontend to only start after there's a working
> network. It started with a user reporting that after upgrading his
> MythBuntu ins
Jaromil wrote:
>> Hi, over on the Samba mailing list, somebody asked what '--with-systemd' was
>> for. It has now degenerated into a discussion on how to get systemd to start
>> the 'samba' deamon,
There's also been a short thread on the MythTV mailing list about how to get
the MythTV Frontend
On Wed, 13 Jul 2016, Rowland Penny wrote:
> Hi, over on the Samba mailing list, somebody asked what '--with-systemd' was
> for. It has now degenerated into a discussion on how to get systemd to start
> the 'samba' deamon, after approx 50 posts on the subject, the discussion is
> still going on.
>
