From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041211 Firefox/1.0

Description of problem:
This is the beginning of the start() function in the ypserv startup
script:

        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
        if [ ! -d /var/yp/$DOMAINNAME ]; then
                exit 1
        fi

If the domainname is not initialized, then it is set to the value of
the NISDOMAIN variable. However, the DOMAINNAME shell variable is
never re-initialized, so the test -d /var/yp/$DOMAINNAME fails.

The fix is obvious, I won't insult you guys by listing it here. :-)

As a workaround, it works on a second run (duh). That's probably what
all the SA's using ypserv on RHEL3 are currently doing...



Version-Release number of selected component (if applicable):
ypserv-2.8-11

How reproducible:
Always

Steps to Reproduce:
1. Set up ypserv on a server, enable it in runlevel 3
2. Reboot
3. Observe how it is not running after the server comes up
    

Additional info:

I'm listing it as severity: high, because a server that refuses to
start when it's supposed to is a rather critical problem. Loss of data
*can* occur if all ypservers are down and no authentication mechanism
is available.