Good point about non-smbd processes being winbindd clients. I've got some myself :-)
Also agreed about benefits of shutting down idle connections -- just not done yet. Ken ________________________________ Ken Cross Network Storage Solutions Phone 865.675.4070 ext 31 [EMAIL PROTECTED] -----Original Message----- From: Michael Steffens [mailto:[EMAIL PROTECTED]] Sent: Saturday, February 15, 2003 11:46 AM To: Ken Cross Cc: 'Mike Sweet'; 'Multiple recipients of list SAMBA-TECHNICAL' Subject: Re: Winbindd limited by select Ken Cross wrote: > I was suggesting the other way around -- the number of winbindd fd's > shouldn't be more than the max # of smbd's (well, maybe a *few* more). But if you are having a system hard limit of 1024 FDs per process, for example, which you can't raise via setrlimit, you could only configure less than that number of smbds. Coupling these numbers does not make sense IMHO for another reason: Every process can become a winbind client, even without knowing about winbind or Samba, via NSS and PAM. How to take these into account? I think winbindd shutting down idle connections (not immediately, there may further requests come along quickly, and never if a connection carries a getpwent/getgrent status) is less trouble. Cheers! Michael
