baselayout-1.12.0_pre17 has removed /etc/init.d/domainname (see bug #129248). However, the initscript of ypbind still depends on it and will not start: # /etc/init.d/ypbind start domainname * ERROR: Some services needed are missing. Run * './ypbind broken' for a list of those * services. ypbind was not started. # /etc/init.d/ypbind broken domainname
This has been worked around already... please emerge --sync
*** Bug 131651 has been marked as a duplicate of this bug. ***
After updating several of our systems this bug has hit us again: baselayout has been updated to -1.12.0_pre19-r2, but ypbind is still at -1.19.1, thus the initscript will never be updated. Could you *please* revbump the ebuild of ypbind?
I just got bit by the lack of rev bump too. Please bump the revision.
*** Bug 142781 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > This has been worked around already... please emerge --sync As my report (142781) is a duplicate of this one, I post here. I have just synced now, but the latest ypserv package available in the portage tree is still 2.19 which has domainname dependencies. Am I missing something (like the meaning ov revbump...) or is it not yet available ?
(In reply to comment #6) > As my report (142781) is a duplicate of this one, I post here. > I have just synced now, but the latest ypserv package available in the portage > tree is still 2.19 which has domainname dependencies. Am I missing something > (like the meaning ov revbump...) or is it not yet available ? Since the package was not revbumped, emerge --sync will not be enough to have the new initscript installed. Try an explicit "emerge -1 ypserv" (followed by "etc-update").
Bumping ypbind won't help, since baselayout unconditionally and forcibly removes /etc/init.d/domainname. I've opened bug #143631, as this is a baselayout problem: no package should ever remove files in /etc/init.d/, and especially not unconditionally, or when they belong to other packages. (And no, setting nis_domain_{interface} in /etc/conf.d/net doesn't do the same, as that will override any domainname received from dhcp)
*** Bug 143631 has been marked as a duplicate of this bug. ***
(In reply to comment #8) > Bumping ypbind won't help, since baselayout unconditionally and forcibly > removes /etc/init.d/domainname. Please, read the changelog. ypbind doesn't _need_ domainname now, it can _use_ it. So, it won't fail any more (re-emerge it and see). And, it does _not_ install /etc/init.d/domainname, don't know where did you get such impression. Can someone revbump the damned thing so that this can be closed?
(While the new version doesn't create /etc/init.d/domainname, it still uses it if present. Sorry for the ambiguity.) No, the new version combined with the new baselayout does *NOT* work: # /etc/init.d/ypbind start * Starting ypbind ... domainname not set - aborting. * No NIS server found [ !! ] nis-domain and nis-servers are provided by the dhcp server. Using /etc/init.d/domainname, and the old version of ypbind and baselayout, this works. As it is now, I have to statically set domainname instead of having it set by dhcp, which breaks failover. Can someone PLEASE restore the old ypbind-1.19.1 from March or thenabouts and version bump the new one, so we at least can mask the new baselayout and ypbind and get the old ones back?
(In reply to comment #11) > Can someone PLEASE restore the old ypbind-1.19.1 from March or thenabouts and > version bump the new one, so we at least can mask the new baselayout and ypbind > and get the old ones back? What do you want to restore? There's nothing changed except "use domainname" instead of "need domainname" http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-nds/ypbind/files/ypbind.initd?r1=1.2&r2=1.3 Sorry, your system is misconfigured, fix it.
(In reply to comment #12) > > Sorry, your system is misconfigured, fix it. I'd love to, but unfortunately, I can't find any pointers as to HOW to fix it. - ypbind won't start without domainname set - domainname doesn't survive reboots - new baselayout won't allow /etc/init.d/domainname which sets domainname Judging by net.example, the following in /etc/conf.d/net should work to get the domainname from the dhcp server: config_eth0=( "dhcp" ) dhcpcd_eth0=( "-D" ) It doesn't -- ypbind fails to start. Looking at /var/log/messages and /var/log/dmesg, it appears that "net" is marked as successfully started *before* dhcpcd returns, which appears to be a change from previous behaviour. Nor will ypbind start if trying a static domainname as per the net.example: config_eth0=( "dhcp" ) nis_domain_eth0=( "example.com" ) If doing this, ypbind STILL won't start, now because domainname is never set. (And it's static too - not set by dhcp, which is what I had working before.) I'd welcome any help from anyone -- are there people here who successfully get ypbind to work with the new baselayout? If so, how do you get domainname set before ypbind is started without the domainname script?
Bumped to fix everyones script. If you want exactly the same behaviour then do this in /etc/conf.d/net dns_domain_lo="foo.com" nis_domain_lo="bar.com"
Thanks; ypbind is looking good now, but it seems you forgot to do the same service for ypserv (cf bug #142781).
*** Bug 169422 has been marked as a duplicate of this bug. ***
