topic nis clients in a domain in Operating System - HP-UX

nis clients in a domain

steven Burgess_2 — Wed, 23 Apr 2003 13:19:28 GMT

Hi all

Quick 10 points. Whats the easiest way to check the number of and hostnames of clients in a NIS domain ?

Thanks in advance

Ste

Re: nis clients in a domain

George_Dodds — Wed, 23 Apr 2003 13:58:34 GMT

Hi Steve nice to see that you've got a proper job at last ;)

Isnt it just one of the yp commands maybe ypcat hosts.

Ta

George

Re: nis clients in a domain

S.K. Chan — Wed, 23 Apr 2003 13:59:37 GMT

Do a ..
# man rpcinfo
and what you can do is run ..
# rpcinfo -b ypbind 1 | more
==> That should list all machines that has ypbind running. Just run it again and pipe it to "wc -l" to get the total. Just keep in mind ypbind is also run on the master and slaves. To get just those you would ..
# rpcinfo -b ypserv 1 | more
or simply ..
# ypcat -k ypservers

Re: nis clients in a domain

Uday_S_Ankolekar — Wed, 23 Apr 2003 14:05:34 GMT

ypcat... is the command.

use ypcat -k ypservers.

Ours is not a NIS setup, but I am sure it's a ypcat command

-USA..

Re: nis clients in a domain

George_Dodds — Wed, 23 Apr 2003 14:15:30 GMT

here's a little ypcat shpeal :)

http://www.informatik.uni-frankfurt.de/doc/man/hpux/ypcat.1.html

Re: nis clients in a domain

Bill Douglass — Wed, 23 Apr 2003 14:25:43 GMT

rpcinfo -b ypbind 1

will return info for hosts on your local subnet. You would need to repeat this for each subnet that is served by your NIS domain.

Check the output from ypcat -k hosts.byname. Presumably, if you are sharing a hosts file by NIS, it will be updated to include the local client names as well as key servers in your domain.

Re: nis clients in a domain

steven Burgess_2 — Wed, 23 Apr 2003 14:33:09 GMT

Hi

Thanks for the replies

ypcat -k ypservers - I had looked at this but it gives me the master and slave

S.K you have given me the number of hosts , thanks

Still not got the names of the hosts in the domain

Ste

Re: nis clients in a domain

Andreas Kruth — Wed, 23 Apr 2003 14:36:52 GMT

Hi,

from the O'Reilly book:
"NFS and NIS"

#! /usr/bin/ksh

( for host in $(ypcat hosts | awk '{print $2}')
do
ypwhich $host
done ) | grep -v 'not-bound' | sort | uniq -c
#EOF

Output:

Maybe helpful

Regards,
Andreas

Re: nis clients in a domain

S.K. Chan — Wed, 23 Apr 2003 14:37:42 GMT

Mmm..
# rpcinfo -b ypbind 1 | more
should give you the IP address in the first column(field) and follow by the hostname in the 2nd column (field).

Re: nis clients in a domain

steven Burgess_2 — Wed, 23 Apr 2003 14:38:47 GMT

Hi

We are using dns for resolution

had checked hosts.byname

Thanks

Ste

Re: nis clients in a domain

Shannon Petry — Wed, 23 Apr 2003 14:41:29 GMT

As far as I know, you wont be able to do this.

ypcat -k ypservers

Only shows you the NIS Database of listed servers.

ypcat hosts

Only shows the NIS map of /etc/hosts from the master server.

rpcinfo will not show you much, because the way NIS works, it is not bound and constantly chatting like winblows. Only when clients need data is there network activity.

So, Im not sure that you can easily do what you want. When I go to a new site, I will usually nmap the whole site, then start telnetting to see how things are configured one at a time.

Regards,
Shannon

Re: nis clients in a domain

steven Burgess_2 — Wed, 23 Apr 2003 14:46:32 GMT

Thanks everyone

I'm off home now. Will respond tomorrow after man utd have beat madrid 3 - 0 (fingers crossed)

Steve

Re: nis clients in a domain

S.K. Chan — Wed, 23 Apr 2003 14:55:14 GMT

On a host that does not run NIS (ie ypbind not running) the ypbind service does not show up in "rpcinfo -p". If you stop nis.client..
# /sbin/init.d/nis.client stop
and run ..
# rpcinfo -p
the ypbind srvice does not show. Start nis.client again and it appears.

Re: nis clients in a domain

Shannon Petry — Wed, 23 Apr 2003 15:03:30 GMT

Your still forced to do this on each client. The rpcinfo method is just as easy as 'ypwhich'. It really makes no difference.

The main problem with achieving the desired results is the way NIS works. Clients are not on "bound" connections.

Historically, this was done for performance. Lord knows we see how slow windblows is with locking connections, and Novell is not much better (used to be worse).

Regards,
Shannon