Date: Thu, 11 Jun 1998 16:29:10 -0600 (MDT) From: Atipa <freebsd@atipa.com> To: Tom <tom@uniserve.com> Cc: John Kenagy <jktheowl@bga.com>, freebsd-stable@FreeBSD.ORG Subject: Re: NIS client maintenance script Message-ID: <Pine.BSF.3.96.980611162450.14678A-100000@altrox.atipa.com> In-Reply-To: <Pine.BSF.3.96.980611154546.10500B-100000@shell.uniserve.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
> There are several problems with the script as attached. > > It assumes only one NIS server ($nis_host). You'd have to be mad to > have only one NIS server in a production environment, especially since > clients can automatically kick over to another if one fails. Correct. This script is not dynamic. I am using it primarily for machines w/o NIS servers on their network. Setting up slave servers would eliminate several problems. > Since all the *pwnam fuctions (getpwnam, getpwent, etc) are flawed in > that they can not return a temporary failure code, such functions should > block until NIS services are back up. This is critical for systems > running mail service, because you don't want all your users to disappear > when NIS goes down. But you don't want to have to wait 14 minutes (7 minutes each for user login, then su) to remedy problems. If no network services are available, your users will go away period, unless they are somehow cached (eg slave server). Suggestions? Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980611162450.14678A-100000>