I increased nscd and slapd threads to 64,
my sarge box is updated with libnss-ldap_238-1.1 from deb-src and
samba_3.0.21a-1 from samba.org,
but the segfaults are presents.
-
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for pid 25710 (/usr/sbin/
reassign 347477 libnss-ldap
thanks
On Wed, Jan 11, 2006 at 01:23:26AM +0100, Samba User wrote:
> 0xb7cea3ae in waitpid () from /lib/tls/libc.so.6
> #0 0xb7cea3ae in waitpid () from /lib/tls/libc.so.6
> #1 0xb7c7fd12 in system () from /lib/tls/libc.so.6
> #2 0x081eb261 in smb_panic2 ()
> #3 0x
On Wed, 2006-01-11 at 07:09 +0100, Christian Perrier wrote:
> > I assumed that this was a problem with nss, nscd or ldap.
> > I've increased the number of concorrent nscd connections
> > from the default 5 to 30 and LDAP connections from the
> > default 6 to 30.
> >
> > Next day I've tested the co
> I assumed that this was a problem with nss, nscd or ldap.
> I've increased the number of concorrent nscd connections
> from the default 5 to 30 and LDAP connections from the
> default 6 to 30.
>
> Next day I've tested the configuration with 31 logins in
> a few minutes. No panic actions reporte
Package: samba
Version: 3.0.14a-3
Severity: important
About 50 users tried to login in a few minutes.
Nearly all logins are succeeded, but on some cliens
a few trials were neccessary. This behaviour is
unusal in our network. I've got about 10 nearly
identical mails from the server about an smbd
p
5 matches
Mail list logo
