| NIS doesn't have any particular knowledge of the contents or format
of items in a given map. So if you have a hosts file in the /var/yp/src
which contains an entry such as:
16.140.32.161 Marvin.zk3.DEC.COM Marvin
then the two keys that get created for this would be "Marvin" and
"Marvin.zk3.DEC.COM" (in hosts.byname)
That is to say, when the map gets created and pushed to the slaves,
and a client should then do a "ypmatch marvin hosts", it won't get
an answer. But if you did "ypmatch Marvin hosts" it would.
So NIS is quite literal and doesn't attempt to canonicalize keys or
what's stored under them.
-- Farrell
[Posted by WWW Notes gateway]
|
| Just some interesting facts after a few tests:
dUnix master with dUnix clients:
no problems managing master host entries like:
162.xx.yy.zz i58hp154 I58HP154 impi IMPI
-> you can access the host using uppercase or lowecase notation
Ultrix-Master with dUnix clients:
-> you can access the host using uppercase or lowecase notation
HP-Master with dUNix clients:
-> you cannot access the host with an entry like above in the master's
host file, when using uppercase notation
but:
HP-Master and SUN clients:
-> no problem accessing a host with an entry like above, using the
uppercase notation
Has anyone the possibility to test if this is correct? Customer wants
an escalation, but I have no possibilities to make tests with HP-UX or
SUNs. Since everything works fine btw. dUnix and dUnix I told him,
there are bad chances for an IPMT.
Regards,
Corina
|