On Jul 17 08:34, Sam Varshavchik wrote: > Despite the outward appearance, systemd is completely ignoring all Before > and After directives. No, it's not. You never replied to my mail in the thread you started a couple of days ago, but before/after do *not* define dependencies. They define an order only. An A after B is satisfied if A started. If it's doing anything useful is totally irrelevant. > [...] > That's because at the time it starts, not all network interfaces are set up, > so it only binds itself to localhost. You can determine it by sifting > through the syslog, looking at what bind is doing at startup. > > In my case, all network servers were frakked up. dhcp. bind. httpd. privoxy. I'm really not sure what you're doing, but my experience is that all my networks services binding to explicit interface addresses failed, and they were started correctly after I added the network-waiter target I posted over in the other thread. There are two problems at work here, one is that the network initscript is broken for a long time (see my bug report at https://bugzilla.redhat.com/show_bug.cgi?id=782042) and the other is that the network target is not defined to be only reached when all network interfaces are up. That's what network-online.target is supposed to accomplish. Corinna -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
