diff -up ypbind-mt-2.5/man/ypbind.8.xml.helpman ypbind-mt-2.5/man/ypbind.8.xml --- ypbind-mt-2.5/man/ypbind.8.xml.helpman 2018-06-04 15:30:38.000000000 +0200 +++ ypbind-mt-2.5/man/ypbind.8.xml 2018-06-07 16:16:56.967024495 +0200 @@ -39,21 +39,33 @@ ypbind - -c - -d -debug - -verbose - -n -forground - -broadcast - -broken-server - -ypset - -ypsetme - -no-ping + + -broadcast + -ypset + -ypsetme + -f configfile + -no-ping + -broken-server -local-only - -ping-interval ping-interval + + + -ping-interval ping-interval + -i ping-interval + + + -d -debug + -v -verbose + -n -foreground + -p port ypbind + -c + -f configfile + + + ypbind --version @@ -88,6 +100,8 @@ Unless the option +or + is used, ypbind detaches itself from the controlling terminal and puts itself into background. ypbind @@ -132,6 +146,57 @@ If the file does not exist or if there a ypbind exit. + +In Fedora we use systemd for starting services. We need to finish starting +process of ypbind service not before service is fully +started, which means ypbind daemon is prepared to answer. +There is a test script /usr/libexec/ypbind-post-waitbind +used in ypbind.service, that waits for ypbind daemon to be +fully connected to NIS server and waits by default up to 45s. Sometimes this +is not enough, because network set up can take longer than 45s during boot, so +starting ypbind.service fails. User can increase the timeout by setting an +environment variable NISTIMEOUT in /etc/sysconfig/ypbind. +For example NISTIMEOUT=180 means ypbind will wait up to 180 +seconds for binding to a NIS server. Another option is to enable +NetworkManager-wait- online.service, which will make ypbind +to wait until network is properly set up. + + + +In case something needs to be changed in the ypbind.service, it is adviced not +to change the ypbind.service directly, but rather to create a new file under +/etc/systemd/system/ypbind.service.d/, i.e. if we need to +start ypbind before service foo.service, we can create file +/etc/systemd/system/ypbind.service.d/wait-foo.conf with +the following content: + + + + +[Service] +Before=foo.service + + + +If you need to pass other arguments to ypbind daemon withing +systemd unit file, you can set these arguments as OTHER_YPBIND_OPTS environment +variable in /etc/sysconfig/ypbind. For example in order to +set a fixed port ypbind should run on, you can specify +OTHER_YPBIND_OPTS="-p 876" in /etc/sysconfig/ypbind. + + + +DHCP client by defualt changes /etc/yp.conf in case DHCP +server sends NIS configuration in the respond. In that case +/etc/dhcp/dhclient.d/nis.sh changes +/etc/yp.conf according such configuration and creates a +back-up copy of the original configuration file into +/var/lib/dhclient/nis.conf.predhclient.$interface. In +order to disable changing /etc/yp.conf by DHCP client, add +PEERNIS=no into /etc/sysconfig/network. + + + @@ -256,6 +321,15 @@ With this options another frequency in s + port + +Lets +ypbind +listen on a specified port number, rather than asking portmapper to assingn a +port for it. + + + Prints the version number diff -up ypbind-mt-2.5/man/yp.conf.5.xml.helpman ypbind-mt-2.5/man/yp.conf.5.xml --- ypbind-mt-2.5/man/yp.conf.5.xml.helpman 2018-06-07 16:29:01.853560699 +0200 +++ ypbind-mt-2.5/man/yp.conf.5.xml 2018-06-07 16:33:59.302833043 +0200 @@ -97,6 +97,14 @@ first the given servers before falling back to broadcasting for a running server. + + Content of /etc/yp.conf can be changed by DHCP client, + for more info see + + ypbind + 8 + . +