Mark Brown wrote:
>
> > The solution was to temporarily run ypbind. It seems that yppush trys
> > to find out the list of slaves from ypbind. As this is a master and is
> > not a NIS client itself, this fails. It should be able to just look in
> > /var/yp/ypservers.
>
> Is there some reason why you actually need to disable ypbind?
I don't as such need to disable it. Enabling it is an effective
workaround for the bug but it remains a bug. Following the howto
document, it is quite logical to setup NISCLIENT=false on a server. The
workaround isn't necessarily obvious so it could cause other people
problems.
The fix would be to make yppush access /var/yp/ypservers directly if the
machine is a master for the domain. yppush's man page states:
It is normally run only on the NIS master by /var/yp/Makefile after
the master databases are changed.
That implies that someone might want to run yppush on some machine other
than a master so it probably still needs to be able to use NIS to get
the list of slaves.
Oliver
This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be copied,
disclosed to, retained or used by, any other party. If you are not an intended
recipient then please promptly delete this e-mail and any attachment and all
copies and inform the sender. Thank you.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
