From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 12 02:34:42 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D79116A4CE for ; Wed, 12 Jan 2005 02:34:42 +0000 (GMT) Received: from S2.cableone.net (smtp2.cableone.net [24.116.0.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91CC343D3F for ; Wed, 12 Jan 2005 02:34:41 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from fennec.local.lan (unverified [24.119.123.89]) by S2.cableone.net (CableOne SMTP Service S2) with ESMTP id 7116095 for ; Tue, 11 Jan 2005 19:55:23 -0700 Date: Tue, 11 Jan 2005 18:34:39 -0600 From: Vulpes Velox To: freebsd-hackers@FreeBSD.org Message-ID: <20050111183439.75e6b334@fennec.local.lan> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IP-stats: Incoming Last 2, First 35, in=54, out=0, spam=0 X-External-IP: 24.119.123.89 X-Abuse-Info: Send abuse complaints to abuse@cableone.net Subject: RC scripts and NIS X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2005 02:34:42 -0000 I am currently am currently working on making modifications to the rc system to allow NIS to not be started if the server is not present. So far I am just looking at disabling ypbind at start if certain conditions are meet. The idea it is to run a script that checks if the servers or server is present and then if it is, ypbind if enabled, if not it modifies the current variables to stop ypbind from being run and prints a message about it to stdout. >From my understanding this is the one that needs disabled if the system is to operate outside of it's usual network. Allowing it to fall back to /etc/ for it's information. I've tested it by disabling it upon startup manually and it worked fine. Is there any other NIS related scripts I should make changes to, or is this the only one I should worry about? If any one have opinions or any input on any of this, I would be interested to hear it.