Al 02/05/10 17:50, En/na Luca Olivetti ha escrit:


2) and with strace I see that pid 2414 got a SIGPIPE writing to fd 8

[pid 2414] write(23, " smbldap_search_ext: base => [s"..., 189) = 189
[pid 2414] rt_sigaction(SIGALRM, {0x803fa895, [ALRM], SA_RESTORER,
0x40328718}, {SIG_IGN}, 8) = 0
[pid 2414] alarm(15) = 0
[pid 2414] time(NULL) = 1272814418
[pid 2414] rt_sigaction(SIGALRM, {0x803fa895, [ALRM], SA_RESTORER,
0x40328718}, {0x803fa895, [ALRM], SA_RESTORER, 0x40328718}, 8) = 0
[pid 2414] alarm(15) = 15
[pid 2414] write(8, "0\204\0\0\0\5\2\1\23B\0", 11) = -1 EPIPE (Broken pipe)
[pid 2414] --- SIGPIPE (Broken pipe) @ 0 (0) ---
Process 2414 detached

I don't see where pid 2414 opens fd 8, either strace didn't catch it or
it was inherited from the parent, but I suppose it's the connection with
the ldap server.

With this data and a little bit of googling, I found a possible problem with nss_ldap. I updated it and now 3.2.6 works fine. Later I'll check if newer versions also work fine.

Bye
--
Luca Olivetti
Wetron Automatización S.A. http://www.wetron.es/
Tel. +34 93 5883004 (Ext.133)  Fax +34 93 5883007
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Reply via email to