Samba Children aren't dying, fighting instead

[David Collier-Brown]

Jeff wrote:
| Things work well for a little while, but as smbd starts spawning
| subprocesses, sometimes 10-15 for a single user, seriously slowing
down
| network response	
...
| Another side effect is that MS Office stops working, and eventually 
| the server "disappears" from the network.  Killing off the obsolete 
| processes solves the problem

	Ok, you have clients disconnecting for some reason.
	As a palliative, set 
	[global] 
		deadtime = 10
	or
		keepalive = 3600
	which will schedule a check every 10 minutes for
	a dead client, followed by the child process cleaning
	up.  Decrease the time as required.

	Look at the logs and see if you can see a sequence of
	connect/diconenct/connect, and see if you can see an
	obvious reason.

	Reasons we've seen in the past include timeouts, possibly
	die to a connectivity problem, shredded packets, due
	to a broken hub/router, and other client or network
	weirdnesses.


	Samba users: should there be a dead time default? if
	so, how much and why?
	
--dave
-- 
David Collier-Brown,  | Always do right. This will gratify some people
185 Ellerslie Ave.,   | and astonish the rest.        -- Mark Twain
Willowdale, Ontario   | //www.oreilly.com/catalog/samba/author.html
Work: (905) 415-2849 Home: (416) 223-8968 Email: davecb at canada.sun.com