On Mon, Feb 21, 2005 at 09:32:56PM +0200, Radu Filip wrote: > That's odd on my side: > > # /etc/init.d/domainname status > * status: stopped
Aha, I think this is our bogeyman. You need to convince the system that domainname is started, somehow. -- aside explaining /etc/conf.d/domainname -- If you run ~x86, the way domainname is configured has changed recently. It happened in a baselayout upgrade. I wonder what version of baselayout you have? I believe the instructions flew by in an einfo or something.. I probably only caught it because I use this enotice patch: http://bugs.gentoo.org/show_bug.cgi?id=11359 (which by the way is _very_ helpful..) If you have the newer baselayout, you should be using /etc/conf.d/domainname instead of /etc/dnsdomainname and /etc/nisdomainname. -- end aside -- However, judging by your comments about /etc/init.d/domainname, it sounds like you are still using the older-style baselayout. > # cat /etc/domainname > mydomain.com I think this is supposed to be /etc/dnsdomainname. IIRC for some stupid reason the error messages are commented out when one of the files is missing :P. > There is no /etc/conf.d/domainname. I tried to move /etc/domainname to > /etc/conf.d/domainname but no good: Yeah that won't work, /etc/conf.d/domainname is not the same as /etc/domainname. > I also looked into /etc/init.d/domainname and I see it is not looking > for any /etc/conf.d/domainname, but for /etc/domainname and > /etc/nisdomainname, which are redundant(?) and both set the same They don't have to be the same, so they're not necessarily redundant. > What is wrong with domainname? Try moving /etc/domainname to /etc/dnsdomainname and starting domainname again. -- gentoo-user@gentoo.org mailing list
