Re: Can't find NIS servers

Chris Cox <notccox@xxxxxxxxxxxxxx> wrote:
Darren Dunham wrote:

It's not a side effect. If your user database comes from NIS and you
need user information, your only choices are to wait for NIS to start or
plead ignorance.


This is a fake requirement. If ypbind fails, you should be able
to use local accounts.

You can use local accounts (depeding on the nsswitch.conf settings).
What you cannot do is know if a non-local account exists or not.

All that is needed is a smart enough
startup (init) to fail ypbind after sufficient tries. I've only
seen this "better" behavior on the Linux platforms.

How does ypbind fail? ypbind should return almost immediately. The
stall is not in starting the NIS client, but in some subsequent startup
file that makes a name lookup.

# /usr/lib/netsvc/yp/ypstart
starting NIS (YP server) services: ypbind done.
# ypwhich
ypwhich: can't communicate with ypbind
# ypwhich
Domain test not bound on sparky.
# ypwhich
Domain test not bound on sparky.
# getent passwd foo
<hang>

--
Darren Dunham ddunham@xxxxxxxx
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
.

Relevant Pages

  • Re: Cant find NIS servers
    ... You can use local accounts. ... My problem is that a box ties to NIS won't boot all the way ... startup to fail ypbind after sufficient tries. ... ypwhich: can't communicate with ypbind ...
    (comp.unix.solaris)
  • Re: Cant find NIS servers
    ... It seems to me whether or not ypbind fails is irrelevant. ... into local lookup calls instead of NIS lookups? ... ypwhich: can't communicate with ypbind ... "I don't want the boot to hang ...
    (comp.unix.solaris)
  • Re: FreeBSD NIS client and Solaris NIS server problem...
    ... > rpcbind debugging enabled. ... > Here are the parameters I'm using in rc.conf for nis: ... Because rpcbind is a dependancy of ypbind, ... If ypwhichdon't tell you more on the hostname of NIS server, ...
    (freebsd-questions)
  • Re: NIS - ypbind not starting on clients at startup
    ... There was bug 221569 (nis: ypbind isn't started on boot), ...
    (Debian-User)
  • adduser re-writting groups file incorrectly
    ... we add a couple local accounts just in case NIS can't be ... account and when the account was created I think it errored on creating ... because it happened to clash with a UID out of NIS. ...
    (freebsd-questions)