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 ?