Yp and a simple question.
Rick Stevens
rstevens at vitalstream.com
Wed Oct 6 21:00:36 UTC 2004
Waldher, Travis R wrote:
>>-----Original Message-----
>>From: Rick Stevens [mailto:rstevens at vitalstream.com]
>>Sent: Wednesday, October 06, 2004 1:35 PM
>>To: Getting started with Red Hat Linux
>>Subject: Re: Yp and a simple question.
>>
>>Waldher, Travis R wrote:
>>
>>>Ok.. I have what I hope is a good question.
>>>
>>>You can set the NISDOMAIN in /etc/sysconfig/network OR in
>>
>>/etc/yp.conf.
>>
>>>You don't have to set it in both.
>>>
>>>Which one is the correct current way to do this?
>>
>>/etc/sysconfig/network, since the ypbind rc.d script uses it.
>> The actual name is set via the "domainname" command, and
>>/etc/rc.d/init.d/ypbind contains:
>>
>>. /etc/sysconfig/network (and "NISDOMAIN=whatever" should be in it)
>>-
>>-
>>-
>> DOMAINNAME=`domainname`
>> if [ "$DOMAINNAME" = "(none)" -o "$DOMAINNAME" = "" ]; then
>> if [ -n "$NISDOMAIN" ]; then
>> action $"Setting NIS domain name $NISDOMAIN: " \
>> domainname $NISDOMAIN
>> else
>> exit 1
>> fi
>> fi
>>
>>
>>
>>>I also found that the only way ypserv was going to build
>>
>>properly, was
>>
>>>to set the nisdomain in the network file. Is there another way?
>>
>>Nope. That's it. Actually, older Solaris systems and such
>>used to have an "/etc/domain" file that contained the NIS
>>domain name. One of their startup scripts did a "domainname
>>`cat /etc/domain`" command to set it.
>
>
> In summary then, would it be accurate to say that yp.conf has been
> depricated?
I'd say yes, but I'd still keep it around and current. ypbind itself
may read it (it used to).
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer rstevens at vitalstream.com -
- VitalStream, Inc. http://www.vitalstream.com -
- -
- Okay, who put a "stop payment" on my reality check? -
----------------------------------------------------------------------
More information about the Redhat-install-list
mailing list