On 08/12/10 15:33 -0400, D G Teed wrote:
Here is what one of the directories looked like:
ls -l 15950/fd
total 0
lrwx------ 1 root root 64 Dec 8 13:52 0 -> /dev/null
lrwx------ 1 root root 64 Dec 8 13:52 1 -> /dev/null
lrwx------ 1 root root 64 Dec 7 15:47 10 -> socket:[38109596]
lrwx------ 1 root root 64 Dec 7 15:47 11 -> socket:[38112677]
lrwx------ 1 root root 64 Dec 8 13:52 12 -> socket:[38129166]
lrwx------ 1 root root 64 Dec 8 13:52 13 -> socket:[38177341]
lrwx------ 1 root root 64 Dec 8 13:52 14 -> socket:[38198508]
lrwx------ 1 root root 64 Dec 8 13:52 15 -> socket:[38256709]
lrwx------ 1 root root 64 Dec 8 13:52 16 -> socket:[38307912]
lrwx------ 1 root root 64 Dec 8 13:52 17 -> socket:[38351349]
lrwx------ 1 root root 64 Dec 8 13:52 18 -> socket:[38378460]
Try doing a 'netstat -e' and see if you can match some of those sockets up
with a connection, and see if you can determine what it's being used for,
and what connection state it's in.
I'm hoping you can tie the down to a particular type of connection, say,
your pam_winbind attempts. If that's the case, then the problem might be
due to a bug in that specific pam module, or could be due to a bug in the
way saslauthd uses pam.
--
Dan White
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
