This is for a lab at home.
In general yes - redundancy is required for anything serious.
However, is there anything that can be done
about timeout?
On Tuesday, October 15, 2024 at 09:16:41 a.m. GMT+9, Philip Guenther
<guent...@gmail.com> wrote:
On Mon, Oct 14, 2024 at 3:52 PM All <olp...@yahoo.ca> wrote:
> I am running ypldap, ypbind, portmap on several client machines.
> Server is running ldapd, ypldap, ypbind and portmap.
> From time to time when the server is no available I am seeing this on clients
> consoles:
> yp_match: clnt_call: RPC: Timed out
>
> Obviously, server is unreachable so errors like this are expected. However,
> is there
> any timeout that can be specified anywhere? Looked at ypldap.conf, but didn't
> find it.
> Also, while the server is unreachable, clients have long boot delays (stuck
> at that error).
> Those clients that were already online have long delay during login on
> console as local root.
> (I can understand having delays with ssh and normal users but why console and
> local root
> are affected?)
> Can anyone kindly point me in the right direction for the solution?
Have redundant (more than one) NIS server.
