* Jan Evert van Grootheest ([EMAIL PROTECTED]) wrote:
> Using these settings, udevd still reports about the ldap server being
> unreachable.
Right, that's expected, and perfectly reasonable.
> But the timeouts are now such that bootup is basically a snap. Each
> search takes about 1 second.
Go
Stephen Frost wrote:
* Stephen Frost ([EMAIL PROTECTED]) wrote:
Right, with the defaults... The idea was to reduce those. I've played
with this some in preparation of 251-6. Try:
reconn_maxconntries = 2
reconn_tries = 1
reconn_sleeptime = 1
reconn_maxsleeptime = 8
I guess I could ha
* Stephen Frost ([EMAIL PROTECTED]) wrote:
> Right, with the defaults... The idea was to reduce those. I've played
> with this some in preparation of 251-6. Try:
> reconn_maxconntries = 2
> reconn_tries = 1
> reconn_sleeptime = 1
> reconn_maxsleeptime = 8
I guess I could have been clearer on th
Stephen Frost wrote:
* Steinar H. Gunderson ([EMAIL PROTECTED]) wrote:
On Tue, Oct 03, 2006 at 11:28:34PM -0700, Steve Langasek wrote:
Can we just fix libnss-ldap already to use a sensible default bind policy,
please?
Sure, I could do that (removing the boot-time workarounds), a
* Jan Evert van Grootheest ([EMAIL PROTECTED]) wrote:
> I've tried it.
I'm not sure you have...
> During boot udevd attempts to resolve a few groups (group scanner, group
> scanner, group scanner, group nvram, user tss, group tss, group fuse,
> group rdma, group rdma), as far as I understand th
* Steinar H. Gunderson ([EMAIL PROTECTED]) wrote:
> On Tue, Oct 03, 2006 at 11:28:34PM -0700, Steve Langasek wrote:
> > Can we just fix libnss-ldap already to use a sensible default bind policy,
> > please?
>
> Sure, I could do that (removing the boot-time workarounds), assuming the
> maintainer d
Steve,
Steve Langasek wrote:
On Wed, Oct 04, 2006 at 02:14:13AM +0200, Steinar H. Gunderson wrote:
The first one is that it attempts to touch a file in a directory that
does not exist. /etc/init.d/libnss-ldap needs /lib/init/rw to exist but
does not make sure.
Simple fix is to create the dir ma
On Tue, Oct 03, 2006 at 11:28:34PM -0700, Steve Langasek wrote:
> Can we just fix libnss-ldap already to use a sensible default bind policy,
> please?
Sure, I could do that (removing the boot-time workarounds), assuming the
maintainer doesn't object...
/* Steinar */
--
Homepage: http://www.sesse
On Wed, Oct 04, 2006 at 02:14:13AM +0200, Steinar H. Gunderson wrote:
> > The first one is that it attempts to touch a file in a directory that
> > does not exist. /etc/init.d/libnss-ldap needs /lib/init/rw to exist but
> > does not make sure.
> > Simple fix is to create the dir manually.
> You're
retitle 390926 libnss-ldap needs a versioned dependency on initscripts
thanks
(Taking it once more, this time in the BTS so others can get an idea of what
I think of the bug(s).)
On Tue, Oct 03, 2006 at 09:22:13PM +0200, Jan Evert van Grootheest wrote:
> Package: libnss-ldap
> Version: 251-5.2
>
Package: libnss-ldap
Version: 251-5.2
Severity: critical
Justification: breaks the whole system
This version of libnss-ldap attempts to do something about the issue
that the ldap server might be unreachable due to not-yet started
services. (i.e. bind-policy soft)
Well. There are two simple techn
11 matches
Mail list logo