On 04/21/2012 08:38 AM, Terry Barnaby wrote: > On 21/04/12 08:10, Terry Barnaby wrote: >> Some update appears to have broken the operation of ypbind recently. >> I have a F14 sever that serves /home and implements NIS services (ypserv) >> and has been running fine for over a year. >> >> The F16 clients use NetworkManager with wired Ethernet set to automatic/system >> connection. Everything comes up fine except for ypbind that fails. This >> has worked fine until a week or so ago (fails on multiple clients). >> >> The boot.log is enclosed, any ideas ? >> >> Cheers >> >> >> Terry >> >> > Enclosed is a portion of /var/log/messages. > > The test.sh entries are a script executed from > /lib/systemd/system/ypbind.service in the "pre" and "post" stages. > > It looks to me that systemd is starting a lot of network services > including the NFS mounts and ypbind before the core network interface > is up and running ... > > Is there a mechanism so that systemd will wait until the "primary" > network is up before continuing ? I assumed that ybind waiting > for "network.target" would have achieved that ? > > > > > For information: You need to run: "systemctl enable NetworkManager-wait-online.service" This sets systemd to wait for the network to be up before generating network.target. Programs then need the network up, such as ypbind, now wait until the network is actually up. Why this is not the default I will never know. I guess most developers are using individual Laptops and not using servers with multiple clients :) -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
