Hi people! I have noticed (and AFAIK it's normal) that samba spawns one server process per client's IP address. Can I change this behavior? Can I somehow force samba to spawn several smbds per client IP? In case of my application (a big x-base accounting program started on NT terminal server) it might be a cure. Currently, when I start several terminal sessions on NT machine with a copy of that accounting thing in each, it (accounting program) dies shortly. When I did an smbstatus' snapshot, I saw that samba spawned ONE smbd process to serve all client processes/requests coming from ONE IP address (that of a terminal server). Accounting program dies when samba opens about 4,500 files. When we started accounting program on separate win workstations, all worked ok since we had several client IPs with a separate daemon for each. At last, here's our configuration: File server: Samba 2.0.7 on FreeBSD 4.2-STABLE, 2xPIII 800 MHz, 512M RAM, h/w RAID-5 Mylex 1100 ~70G Terminal server: NT4 terminal server edition, Cytrix MetaFrame, 2xPIII 800 MHz, 1G RAM, 10G SCSI HDD (system) Thanks for your attention, -- Yours truly, WBR, Paul Argentoff. +------------------------------------------------------- | e-mail: Paul Argentoff <argentoff@rtelekom.ru> | homepage: http://www.chat.ru/~argentof +--------------------------------------
> I have noticed (and AFAIK it's normal) that samba spawns one server > process per client's IP address. Can I change this behavior? Can I somehow > force samba to spawn several smbds per client IP? In case of my application > (a big x-base accounting program started on NT terminal server) it might > be a cure.The fix is a NT (Terminal Server especially) registry setting: HKEY_LOCAL_MACHINE: SYSTEM / CurrentControlSet / Services / rdr / parameters Add the key - MultipleUsersOnConnection: REG_DWORD 0 This will tell the NT (terminal) server to start a new connection to the samba server for each network connection vs. the samba server. There are some info about this in the install-docs for Samba. The Microsoft KnowledgeBase also has this info. Regards Per Kjetil Grotnes --- IT-Seksjonen, Plan- og bygningsetaten, Oslo Kommune Tlf: 22 66 26 61, Fax: 22 66 26 65
> The fix is a NT (Terminal Server especially) registry setting: > HKEY_LOCAL_MACHINE: > SYSTEM / CurrentControlSet / Services / rdr / parameters > Add the key - MultipleUsersOnConnection: REG_DWORD 0Argh, I have to correct myself. This is a VALUE not a KEY under "parameters". Regards Per Kjetil Grotnes --- IT-Seksjonen, Plan- og bygningsetaten, Oslo Kommune Tlf: 22 66 26 61, Fax: 22 66 26 65
Paul Argentoff wrote:> > Hi people! > > I have noticed (and AFAIK it's normal) that samba > spawns one server process per client's IP address. Can > I change this behavior? Can I somehow force samba > to spawn several smbds per client IP?Not currently.> Currently, when I start several terminal sessions > on NT machine with a copy of that accounting thing > in each, it (accounting program) dies shortly. > When I did an smbstatus' snapshot, I saw that samba > spawned ONE smbd process to serve > all client processes/requests coming from ONE IP > address (that of a terminal server). Accounting > program dies when samba opens about 4,500 files.Yes. We know this is a problem and are considering ways to rememdy the situation.> Terminal server: NT4 terminal server > edition, Cytrix MetaFrame, 2xPIII 800 MHz, 1G RAM, 10G > SCSI HDD (system) > Thanks for your attention,Oh. I thought you were talking about win2k TSE. For NT4 TSE, try the following registry setting on the Terminal Server. [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters] "MultipleUsersOnConnection"=dword:00000000 You will need to reboot after merging the setting of course. (or maybe just restarting the Workstation service) Cheers, jerry ---------------------------------------------------------------------- /\ Gerald (Jerry) Carter Professional Services \/ http://www.valinux.com/ VA Linux Systems gcarter@valinux.com http://www.samba.org/ SAMBA Team jerry@samba.org http://www.plainjoe.org/ jerry@plainjoe.org "...a hundred billion castaways looking for a home." - Sting "Message in a Bottle" ( 1979 )
On Mon, 5 Feb 2001 14:36:24 +0100 Grotnes Per Kjetil PBE-SIT <PerKjetil.Grotnes@pbe.oslo.kommune.no> wrote: GPKPS> The fix is a NT (Terminal Server especially) registry setting: [skipped] GPKPS> There are some info about this in the install-docs for Samba. The Microsoft GPKPS> KnowledgeBase also has this info. Could you please tell me where exactly? Or in what section? -- Yours truly, WBR, Paul Argentoff. +------------------------------------------------------- | e-mail: Paul Argentoff <argentoff@rtelekom.ru> | homepage: http://www.chat.ru/~argentof +--------------------------------------
> GPKPS> The fix is a NT (Terminal Server especially) registry setting: > Could you please tell me where exactly? Or in what section?http://support.microsoft.com/support/kb/articles/Q190/1/62.asp This fix is for the 2048 open file limitation. The effect is that instead of having one virtual circuit for the entire WTS (one smbd on the samba server) you get one virtual circuit for each client (which mean users in a windows terminal server environment). And voila! You have one smbd for each user connecting to the samba server. I have deleted the source directory so I cant point you to the samba doc-file for this. Wouldnt be much problem for you to find it... yourself... if you have the source-directory intact. regards Per Kjetil Grotnes --- IT-Seksjonen, Plan- og bygningsetaten, Oslo Kommune Tlf: 22 66 26 61, Fax: 22 66 26 65