Hello list
The below mentionned problem just occured again.
We had about 673 smbd Processes running and 1746
Locks (as reported by smbstatus) when it happened.
Again, the only unusual thing smbd.log said was:
8<
[2007/11/01 15:44:14, 0]
On 26.10-14:43, Arnaud FLORENT wrote:
>
> I had same problem using ldap on sarge with samba 2...
> after stopping samba with init script smbd process remaining...
>
> upgrading libnssldap resolve my problem
Hello Arnaud
We don't use nss_ldap anymore because the Domain Controllers
couldn't h
Hello
I had same problem using ldap on sarge with samba 2...
after stopping samba with init script smbd process remaining...
upgrading libnssldap resolve my problem
Christoph Kaegi a écrit :
On 25.10-15:02, Mike Eggleston wrote:
A recent problem I had of hundreds of smbd processes runnin
On 25.10-15:02, Mike Eggleston wrote:
>
> A recent problem I had of hundreds of smbd processes running
> for only 15 users was fixed by adding 'deadtime = 60' to the
> global section of /etc/samba/smb.conf.
Thanks for the answer Mike
We already had deadtime=1, but that didn't seem to help.
Chri
On Thu, 25 Oct 2007, Christoph Kaegi might have said:
>
> Hello list
>
> Our central fileserver is a Samba 3.0.25b on Solaris 9 and has
> 10'000 users (several hundreds at the same time).
>
> This week it died on us and when I inspected the machine, it
> was out of 8GB Memory and 16GB Swap bec
Hello list
Our central fileserver is a Samba 3.0.25b on Solaris 9 and has
10'000 users (several hundreds at the same time).
This week it died on us and when I inspected the machine, it
was out of 8GB Memory and 16GB Swap because thousands of
smbd processes were running.
netstat -na showed that
