Re: Need help with NIS: close, but it don't work yet
On 11 Oct 1996, Miquel van Smoorenburg wrote:
> >A year ago I tried out NIS and had it working on my Slackware system.
> >(I didn't actually need to use it, so I only ran it for a day.)
>
> Ah I see what you want.
>
> You don't need NIS to resolve hostnames. In fact, I'm pretty sure the
> This week a new version of the GPL ypbind (3.00) was announced. I'll
>
> Until then, you could get the new ypbind-3.00 yourself and put it
> in /usr/local/bin. That should get you started.
>
> ftp://ftp.uni-paderborn.de/pub/linux/local/yp/ypbind-3.0.tar.gz
I did see this announcement, but didn't think much of it. I'm so used
to everything working well on my Linux system that the possibility of
needing a newer version of ypbind didn't even cross my mind.
So, within minutes of getting your mail I had downloaded, compiled and
installed this new ypbind.
And, it _works_, just fine! Thank-you!
There is an issue, however. I'm on an ISDN line to the office. We like
the feature that ISDN drops the line after a period of inactivity. Then,
you just hit a key (or jiggle the mouse in an X-app window), and within
a second the ISDN connection is back up.
ypbind checks that the NIS server is still there every minute (the period
in the old version. The new man page just says "periodically").
The man page doesn't show an option to override this, so I may just
put one in myself. Do you see any problem with this?
BTW, you mentioned that I should just use DNS. I agree, and would prefer
to do so, but I can't seem to get past the firewall in the office to the
DNS server at the ISP. With ppp I could, but not with this new isdn
connection. The big difference is that I'm on a different subnet now.
We've opened up the firewall to this subnet. All other services (ftp,
telnet, etc) are OK but not DNS. That's why I've gone to NIS for now.
The NIS server is on the inside of the firewall, and passes outside name
resolution to the ISP's DNS server.
Lastly, here are a couple of corrections to the nis.debian.howto:
3. If you don't trust your network, edit /etc/init.d/nis and add a list
of your NIS servers after the call to ypbind like this:
ypbind -S nisserver
or
ypbind -S nisserver1,nisserver2,nisserver3
Two things here. The man page says: -S domain,server...
so your example should be ypbind -S domainname,nisserver, etc.
Also, the /etc/init.d/nis file is calling start-stop-daemon, so the
parameters actually need to be added like this:
start-stop-daemon --start --quiet --exec ${NET}/ypbind -- -S veritas,192.159.106.123
The new ypbind version 3 doesn't use the -S option anymore, so these
corrections are probably history anyway.
...RickM...
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: