Date: Sat, 12 Aug 2006 09:00:13 -0700 From: "Atom Powers" <atom.powers@gmail.com> To: "Pramod Venugopal" <pramod@dvnull.org> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Slow Startup with nss_ldap Message-ID: <df9ac37c0608120900u6b82d144yd18cfa9a89472f47@mail.gmail.com> In-Reply-To: <DAC3BE08-0477-4E4D-A5ED-12BC90D365EF@dvnull.org> References: <DAC3BE08-0477-4E4D-A5ED-12BC90D365EF@dvnull.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Try starting ldap first, using rc.d magic. Try putting 'bind-policy soft" (sp?) in your nss_ldap.conf, ldap.conf On 8/11/06, Pramod Venugopal <pramod@dvnull.org> wrote: > 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 > > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > -- -- Perfection is just a word I use occasionally with mustard. --Atom Powers--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?df9ac37c0608120900u6b82d144yd18cfa9a89472f47>