On Mon, 21 Feb 2005, N. Owen Gunden wrote:

> All of that looks OK (exactly like what I'm running, in fact).  I wonder
> if you've got some kind of circular dependency with domainname?  (Have
> you changed any /etc/init.d scripts?)

No, I didn't changed anything

>  Make sure domainname, hostname,
> and portmap are "running" with:
>
> /etc/init.d/domainname status
> /etc/init.d/hostname status
> /etc/init.d/portmap status
>
> And I assume you've set /etc/conf.d/domainname?  (NISDOMAIN needs to be
> set.)

That's odd on my side:

# /etc/init.d/hostname status
 * status:  started
# /etc/init.d/domainname status
 * status:  stopped
# /etc/init.d/portmap status
 * status:  started

# /etc/init.d/domainname start
 * Setting NIS domainname to mydomain.com...        [ ok ]
# /etc/init.d/domainname status
 * status:  stopped

# cat /etc/domainname
mydomain.com
# cat /etc/nisdomainname
mydomain.com

There is no /etc/conf.d/domainname. I tried to move /etc/domainname to 
/etc/conf.d/domainname but no good:

# mv /etc/domainname /etc/conf.d/
# /etc/init.d/domainname start
/sbin/runscript.sh: line 1: mydomain.com: command not found
 * Setting NIS domainname to mydomain.com...       [ ok ]
# /etc/init.d/domainname status
/sbin/runscript.sh: line 1: mydomain.com: command not found
 * status:  stopped

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

What is wrong with domainname?
  Radu
--
[email protected] mailing list

Reply via email to