I have hundreds of the 'smb -D' processes over several days running on my primary samba box that serves home directories, shared directories, etc. This is a Fedora Core 5 box with the latest OS patches. Glancing through the smb.conf file I didn't see anything that looked like it would allow hundreds of processes. I ran a strace on one of the early processes and it seemed to be in a wait state. I'm at home for now and cannot look at the box until tomorrow morning. Any guesses on what might be going on and how to fix it? Mike
On Tue, 31 Jul 2007, mikee might have said:> I have hundreds of the 'smb -D' processes over several days > running on my primary samba box that serves home directories, > shared directories, etc. This is a Fedora Core 5 box with the > latest OS patches. > > Glancing through the smb.conf file I didn't see anything that > looked like it would allow hundreds of processes. > > I ran a strace on one of the early processes and it seemed to > be in a wait state. I'm at home for now and cannot look at the > box until tomorrow morning. > > Any guesses on what might be going on and how to fix it? > > Mike > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/sambaI found at a mac site (http://www.macwindows.com/OSXServer.html) mention of a smb.conf parameter I had not seen/used before. I've modified my $host:/etc/samba/smb.conf to have a 'max smbd processes = 20' entry in the global section. Now I'll wait and see what happens (I've also restarted). Mike
Hi Mike, I've encountered this one too. The solution was to add an smbd deadtime. As I understand the issue, XP and Samba don't always agree when an SMB session should be closed. Try adding: deadtime = 60 which means "If I don't hear from a client within 60 minutes, assume that the connection is dead and close the smbd process". Also see my bug report at https://bugzilla.samba.org/show_bug.cgi?id=4470 Regards, Patrick
Maybe Matching Threads
- Installing windows drivers into print$ on OS X 10.5 Leopard
- Fw: Mac OSX Tiger 10.4.2 SMB
- High CPU load with multiple SMB processes with Yosemite clients
- Locking problems on a Windows server with samba OSX clients
- Accumulating smbd processes and sockets in CLOSE_WAIT state