On Wed, 2017-01-18 at 21:25 -0600, Chris Adams wrote: > Once upon a time, Rick Stevens <ricks@xxxxxxxxxxxxxx> said: > > 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. > > That's not true. systemd distinguishes between starting the network and > the network being available. What is a bug is that a bunch of services > depend on the first, not the second, and they don't start right (or at > all, depending on config) when the network isn't actually available yet. > > Any service that can be configured to bind to a specific IP should have > "After=network-online.target" rather than "After=network.target". This > can be servers for web, mail, FTP, SSH, DNS, logging, and more. > > This is a long-standing service configuration bug, not any inherent > problem with systemd. > > https://bugzilla.redhat.com/show_bug.cgi?id=1119787 Just as a matter of interest, why does "After=network.target" even exist? In what circumstance would this ever be the right thing to do? poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
