I am finding on my systems that ypbind is failing occasionally at boot
(about 30% of the time).
[ OK ] Started Network Manager Wait Online.
[ OK ] Reached target Network is Online.
Mounting /src...
Mounting /scratch...
Starting NIS/YP (Network Information Service) Clients to NIS
Domain Binder...
Mounting /home...
Mounting /opt...
Mounting /dist...
Starting Notify NFS peers of a restart...
Starting Beam BOAP Name Server...
Mounting /usr/beam...
Mounting /var/cache/dnf...
[ OK ] Started Notify NFS peers of a restart.
[ OK ] Started Beam BOAP Name Server.
[FAILED] Failed to start NIS/YP (Network Information Service) Clients to
NIS Domain Binder.
See 'systemctl status ypbind.service' for details.
[ OK ] Reached target User and Group Name Lookups.
The error is:
Feb 1 10:34:36 beam1 ypbind[788]: No NIS server and no -broadcast
option specified.
Feb 1 10:34:36 beam1 ypbind[788]: Add a NIS server to the /etc/yp.conf
configuration file,
Feb 1 10:34:36 beam1 ypbind[788]: or start ypbind with the -broadcast
option.
But /etc/yp.conf has:
# generated by /sbin/dhclient-script
domain beamnet server 192.168.201.1
ypbind starts fine after the system has booted.
I assume that ypbind is being started by systemd before the dhcp client
has actually written into /etc/yp.conf.
Does the system " target Network is Online" get reached after DHCP
configuration ?
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
