From owner-freebsd-questions@FreeBSD.ORG Sat Aug 12 03:39:33 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93FA916A4DA for ; Sat, 12 Aug 2006 03:39:33 +0000 (UTC) (envelope-from pramod@dvnull.org) Received: from thor.novesolutions.com (thor.novesolutions.com [64.127.103.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C26F43D68 for ; Sat, 12 Aug 2006 03:39:28 +0000 (GMT) (envelope-from pramod@dvnull.org) Received: from [192.168.1.90] (c-67-168-71-246.hsd1.wa.comcast.net [67.168.71.246]) by thor.novesolutions.com (Postfix) with ESMTP id C82C4577F3 for ; Fri, 11 Aug 2006 20:39:28 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v749.3) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-questions From: Pramod Venugopal Date: Fri, 11 Aug 2006 20:39:19 -0700 X-Mailer: Apple Mail (2.749.3) Subject: Slow Startup with nss_ldap X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2006 03:39:33 -0000 Hello everyone, I have a FreeBSD 6.1-RELEASE system configured as a Samba Server with an OpenLDAP backend. I have configured nss_ldap to allow local user authentication via LDAP. However if I reboot this machine for any reason, the bootup process gets stuck on named. If I Ctrl-C out of named, it gets stuck again on slapd. However, if i put the original nsswitch.conf back, the machine boots up fine and i have to copy the old nsswitch.conf back to get local user authentication. Here is the updated nsswitch.conf file: --8<-- passwd: files ldap group: files ldap --8<-- From looking at the logs, it looks like these processes are trying to access the ldap server which isnt up since it has not started yet. Is there any way I can get past this (other than using the original nsswitch.conf and changing back manually)? Thanks in advance, Pramod Venugopal