From owner-freebsd-current@FreeBSD.ORG Thu May 27 02:31:59 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFB3D106564A for ; Thu, 27 May 2010 02:31:59 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by mx1.freebsd.org (Postfix) with ESMTP id 8D1DD8FC08 for ; Thu, 27 May 2010 02:31:59 +0000 (UTC) Received: by qyk11 with SMTP id 11so10638317qyk.13 for ; Wed, 26 May 2010 19:31:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=UjkCwPxNRLBjEIXNBHpRQqxJRGr8H75vvsJ94I58NUY=; b=s8ejCdUa3Mcr4esIeoYN9PaXJCs7N3D4/3Ts9Bj1yb3kWeJ5BIfRlWIMoo5xgFYEFY 0C45+uqkSE+McxUwcIIAmSwRzoy6Y4Z2sKYtN1kC3BNC4iPHM9dhklKWbhSJjwEWQr7w gSwdIFf920yGEWT0Rz0rmxwkObLdcCf+U4QqE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=RlCikuCLGA6vtk1Ee0ayXbxunSeQF91W1G+qsv+6TkZyBjK2218AqnSb1W9jNfFk00 P3oN20yrBBDgtzdo5BMpSgkW9A+Vm6fVFp1znPeiP+N8lz2DdnsHZNMrQWEou86cfBFA AAcuGqWxAU89qGQEl2xbl1sG7iM6p526uzYyw= MIME-Version: 1.0 Received: by 10.229.250.206 with SMTP id mp14mr2126302qcb.62.1274927518658; Wed, 26 May 2010 19:31:58 -0700 (PDT) Received: by 10.229.190.83 with HTTP; Wed, 26 May 2010 19:31:58 -0700 (PDT) Date: Wed, 26 May 2010 19:31:58 -0700 Message-ID: From: Garrett Cooper To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 Subject: NIS crankiness at bootup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2010 02:31:59 -0000 Hi folks, I've been booting from NIS off a development machine at work and I've noticed the following behavior: 1. Booting with nisdomainname, nis_client_enable, nis_client_flags set at boot makes the machine inaccessible (I have to reboot the machine, get into singleuser, comment out the vars, and boot again). 2. Booting with the variables unset, uncommenting them, booting up, and finally enabling all of the amd and NIS bits works. So I was wondering if there was some secret sauce in the mix or some monkeying that I needed to do (similar to ntpdate to ensure that the interface is up and functional) to determine that NIS is sane and functional for use, or is there some option I can specify in nsswitch.conf to fallback to the system account data)? Thanks, -Garrett