On 19/1/17 11:28 am, Matthew Miller wrote:
On Wed, Jan 18, 2017 at 04:37:34PM -0800, Rick Stevens wrote:
I think the issue here is that systemd is non-determinate as to when
things actually get done. systemd simply spawns off some command, flags
itself saying "Ok, that's done" and then goes off on its merry way. It
doesn't verify that what was done actually GETS DONE. So, it launches
the network, says the network is up and moves along even though the
network isn't actually up. Your mount is sometimes attempted with a
functioning network and sometimes not. You're left to figure out why.
This is not correct for systemd's network targets. Somewhat ironically,
this is actually an improvement over sysv init. See
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
Stephen, are you using NetworkManager?
I am still using NetworkManager, but I am having problems with it at the
moment with it not connecting to my usb wireless device, which I'm still
trying to sort out.
regards,
Steve
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
