search for: gorlier

Hi there, We are thinking about sharing same files: - OS2/Win clients with Samba - Linux clients with NFS. So, the same files would be shared by 2 different protocols. Looking at the open.c samba code, there seems to be no check / no error (sharing violation) returned to the smb client when the file is already locked by an NFS client. - So, even if a file is opened and locked by an NFS client,

Hi, We're doing some of performance tests with Linux Samba v3. We're comparing WinXP/Win2k clients vs OS2 clients accessing a samba server. For one test, we're coping 10.000 small files. Let's say, we run the command copy \\sambaserver\10000files\*.* c:\data\10000files With an OS2 client it takes 23 seconds to complete. With an Windows client it takes 460 seconds to complete.

As described in the Samba documentation, one smbd process is started for each new session/connection. When a new client connects to a Samba server, a new smbd process is started. During out tests, we noticed that : - The owner of this smbd process on the samba server is the id of the client . - If the client is inactive for 60 seconds, the owner of smbd process become "root". - If

We are currently trying to limit the number of processes/connections on our samba server. Our current version is Samba version 3.0.23c-SerNet-RedHat. We tried to use the deadtime parameter. If we set deadtime to 3 (3 minutes), the connection that is not used by the client for more than 3 minutes is still seen in the smbstatus and net status sessions. The corresponding smbd process is still

Doing some other tests, we determinate that the problem occurs when Fileservers and Ldap servers are not on the same IP subnet. When they are on different subnets, the TCP timeout is about 3 minutes. We could change some kernel IP settings (as syn_retries) but we do not want to do that....another side effects would occur.... As the samba 'ldap timeout' parameter seems to be effective

Hi, We're doing some of performance tests with Linux Samba v3. We're comparing WinXP/Win2k clients vs OS2 clients accessing a samba server. For one test, we're coping 10.000 small files. Let's say, we run the command copy \\sambaserver\10000files\*.* c:\data\10000files With an OS2 client it takes 23 seconds to complete. With an Windows client it takes 460 seconds to complete.