I emerged ypbind-1.11-r1 but couldn't successfully execute /etc/init.d/ypbind. It started ypbind daemon but init script exited with error "No NIS server found". I had to comment out portion of the init script to make it work. start() { checkconfig || return 1 ebegin "Starting ypbind" ypdomainname "$YP_DOMAIN" start-stop-daemon --start --quiet --exec /usr/sbin/ypbind #if [ -n "$?" ] ; then # notfound=1 # for i in 0 1 2 3 4 5 6 7 8 9 # do # ypwhich &>/dev/null && { notfound=0; break; } # sleep 1 # done # if [ $notfound -eq 1 ] ; then # eend 1 "No NIS server found" # fi #else # eend $? #fi }
I had a similar problem just now. My box Gentoo 1.2 ran fine with dhcpcd and ypbind for 6 months. Then over the weekend did a emerge sync and dhcpcd was updated. No NIS Server found! on reboot. I investigated. I saw my yp.conf had been replaced. I fixed it up but on reboot it was again replaced. Ok, dhcp is interfering with NIS then. man dhcpcd says -Y stop dhcp from overwriting yp.conf, stops updating hostname as well -D allow for hostname updating if using -Y So I think to fix this, the right way, one must edit: /etc/init.d/net.ethx and line: local dhcp_args="$(eval echo \$\{dhcpcd_${IFACE}\})" must be changed to: local dhcp_args="-D -Y $(eval echo \$\{dhcpcd_${IFACE}\})" It works now for me again. The -Y flag on dhcpcd is critical if using: ypserver hostname in yp.conf. Marcel
Created attachment 16253 [details, diff] small ypbind patch here is a patch which simply adds some einfo at the end of the emerge warning the user to update their dhcp_eth0 flags. is this sufficient to close this one?
Anyone care about this anymore? Brad, would you mind applying the tiny patch and closing the bug as resolved? Thanks..
The latest version of ypbind-mt, is 1.16. The stable x86 version in gentoo is 1.11-r1, which hasn't been updated in more than a year. Is the ypbind package still maintained?
Created attachment 25375 [details] updated ypbind ebuild This is an ebuild for ypbind-1.16. It's been updated by simply copying the 1.12 version (patched with the warning message discussed on this bug). I've cranked the new version up and it works fine. I've some experience with these ebuilds as I've updated them a couple of times. I would recommend adding ypbind-1.16.ebuild (this attachment) to the tree in ~x86, and then flipping 1.12 over to x86.
Alright, ypbind 1.17.2 is now in the tree, with the added patch. Marking this as fixed
