[Samba] Samba limits on HPUX???

[reinout.wijnveen at philips.com]

Paul,

I'm not sure if this is true for read only shares. But we have run into similar problems due to the kernel parameter nfile (number of available filelocks) which defaults to 200 on HP-UX.   In our case this limits the number of users to about 20. Samba
complains loudly about this situation: it has no locks available to open it's .tdb. Please check for such messages in your logs.

You can safely increase (reboot required of course) this to, say, 5000. It takes about 100 /120 bytes of system memory per configured filelock. You may also want to check the usage of this parameter with glance or gpm before you make any changes


-
Regards,
Reinout Wijnveen

"All those who believe in psychokinesis raise my hand"

ICT-N/Philips Semiconductors Nijmegen
Address: AC 0.061, Gerstweg 2, 6534 AE Nijmegen
Fax: +31 24 353 2019
Tel.  +31 24 353 3631


                                                                                                                        
                      Joseph Loo                                                                                        
                      <jloo at acm.org>               To:  samba list <samba at lists.samba.org>                              
                      Sent by:                     cc:  (bcc: Reinout Wijnveen/NYM/SC/PHILIPS)                          
                      samba-admin at list             Subject:   Re: [Samba] Samba limits on HPUX???                       
                      s.samba.org                                                                                       
                                                   Classification:                                                      
                                                                                                                        
                      03/20/02 03:30                                                                                    
                      PM                                                                                                
                                                                                                                        
                                                                                                                        




I am not sure, but most Unix and Linux system has a file descriptor and
number of processes allowed. The file descriptors are important because
I believe each open file or tcp/ip connection requires a file
descriptor. The file descriptors are limited both on a global basis and
a per process basis. An example is ulimit -a will show some of the
limitiation associated with an open session. Note, this may not be
applicable to the process that started to the smb especially the file
descriptor
limitiation. The global process limitiation may limit you. The process
limit is important because it limits the number of processes a single
process can start.

You might want to check out your system and see what your file
descriptor and process limitiation and see if your machine is exceeding
the global limits.

Orwig, Paul wrote:

>We are using SAMBA 2.2.3a on HPUX 11.0 and are running into a problem where
>after 30 sessions, noone else can access the shares.
>
>We have eight 60 GB read-only shares.
>
>Our test consists of a batch file that checks 64 times for the command file
>on one of the shares. We get around 30 sessions running and everything after
>that fails to find the command file.
>
>Are there limits in SAMBA on sessions/shares/locks ???
>
>Is there something in HPUX that would limit samba sessions?
>
>Guidance and counsel, please!
>
>Paul Orwig
>Pacific Life
>

--
Joseph Loo
jloo at acm.org



--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba