I'm running Debian unstable (sid), and after a recent (several weeks ago) apt-get upgrade, nis (client) started having some problems. Upon startup it will bind to the domain, but it won't start the ypbind service. I always have to do it manually after startup. The rc script is running because it prints "Starting NIS services: ", but it doesn't print ypbind. After startup, when I run the service it works just fine: "Starting NIS services: ypbind". I guess if no one has seen this, then I'll just debug by stepping through the rc script to see what's killing it.
Casey
signature.asc
Description: This is a digitally signed message part
____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
