Hi, I have just compiled and installed Samba vers. 2.2.0 at a HP-UX 11.00 system. I now have the problem that a smbd process is started for each individual share a user access.Previously in vers. 2.0.7 one process were started for each user serving all the shares the user access at the server. Has anybody have a solution to prevent this or eventually just an explanation for the behaviour? Best regards Claus Svarer -------------- next part -------------- A non-text attachment was scrubbed... Name: csvarer.vcf Type: text/x-vcard Size: 394 bytes Desc: Card for Claus Svarer Url : http://lists.samba.org/archive/samba/attachments/20010420/f709a176/csvarer.vcf
Hi, I too have just compiled and installed the just-released 2.2.0 version on HPUX 11.00, but I am NOT having the same problem that you have. On my system, the number of SMBD process is always equal to the number of active client connections PLUS 1. This is the exact same behavior as in 2.0.7 When you said "a smbd process is started for each individual share a user access", how exactly are the users accessing the shares? I just want to get an exact duplication scenario. Claus Svarer wrote:> Hi, > > I have just compiled and installed Samba vers. 2.2.0 at a HP-UX 11.00 > system. I now have the problem that a smbd process is started for each > individual share a user access.Previously in vers. 2.0.7 one process > were started for each user serving all the shares the user access at the > server. > > Has anybody have a solution to prevent this or eventually just an > explanation for the behaviour? > > Best regards > Claus Svarer-------------- next part -------------- A non-text attachment was scrubbed... Name: corny.vcf Type: text/x-vcard Size: 334 bytes Desc: Card for Cornelio Bondad Url : http://lists.samba.org/archive/samba/attachments/20010420/70581206/corny.vcf
Hi Claus, I am using 2.2.0 released tarball on HP-UX 11.0 as well, and do not experience this. I get one smb per client, not per share. One thing that could cause this behavior is if the smbd that is servicing the client is 'hung' somehow, so that when the next attempt is made from the client, it thinks it has to renegotiate, etc and starts up a new smbd. I would suggest turning on log level = 10, debug pid = yes and log file /usr/local/samba/var/log.%m Then reproduce this behavior; possibly you will see the last thing done on the previous pid for the original smbd that was created for the client, and the one that gets created when you attach to the next share; whatever it was last doing is probably where you're hung up... Just a thought, Don -----Original Message----- From: Claus Svarer [mailto:csvarer@nru.dk] Sent: Friday, April 20, 2001 5:29 AM To: samba@lists.samba.org Subject: Samba 2.2.0, number of SMBD's processes Hi, I have just compiled and installed Samba vers. 2.2.0 at a HP-UX 11.00 system. I now have the problem that a smbd process is started for each individual share a user access.Previously in vers. 2.0.7 one process were started for each user serving all the shares the user access at the server. Has anybody have a solution to prevent this or eventually just an explanation for the behaviour? Best regards Claus Svarer