Well... in fact, I don't think this is quite so...

The problem is how much time does ypbind take to actually start up and
bind to the nis server...

My guess is that if this is run on the server itself it should be
somehow quick and otherwise, it will depend on network condition and nis
server responsivenes...

The point is that this is actually not an error condition but merely a
warning and giving this a few more seconds may or may not help,
depending on how soon you will _actually_ need the nis services up and
binded to the server...

Here's what the startup script /etc/init.d/nis is doing in the
bind_wait() function:

bind_wait()
{
    [ "`ypwhich 2>/dev/null`" = "" ] && sleep 1

    if [ "`ypwhich 2>/dev/null`" = "" ]
    then
        bound=""
        log_action_begin_msg "binding to YP server"
        for i in 1 2 3 4 5 6 7 8 9 10
        do
            sleep 1
            log_action_cont_msg "."
            if [ "`ypwhich 2>/dev/null`" != "" ]
            then
                echo -n " done] "
                bound="yes"
                break
            fi
        done
        # This should potentially be an error
        if [ "$bound" ] ; then
            log_action_end_msg 0
        else
            log_action_end_msg 1 "backgrounded"
        fi
    fi
}


So... it gives it 10 times 1 second + the time to run ypwich to actually bind 
the server.

The point is that even if this fails, ypbind is still running and, if
there is a server available for the configured domain, it will
eventually find it.

If you want to speed your boot times y _may_ want to try reducing the
tries (which are blocking the next startup scripts from running) and
replace the "for" line with a shorter one like:

        for i in 1 2 3
        do
            sleep 1
            log_action_cont_msg "."
            if [ "`ypwhich 2>/dev/null`" != "" ]
            then
                echo -n " done] "
                bound="yes"
                break
            fi
        done


Give it a try if you want, but I don't think _this_ kind of thing will be 
commited to the distro... I don't have a nis setup here at home to try this out 
and won't be at the office until Monday.

-- 
NIS fails to bind to YP server during boot
https://bugs.launchpad.net/bugs/354588
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to