search for: altissemiconductor

...conf but it does not help. ( from 5 to 600) We have tried using smaller and greater values in the /etc/ldap.conf for bind_timelimit and timelimit (30 by default, from 5 to 300), but it does not help. Here is our smb.conf related to ldap : passdb backend = ldapsam:"ldap://itdsd1l1.altissemiconductor.com ldap://itdsd2l2.altissemiconductor.com" ldap passwd sync = Yes ldap admin dn = cn=samba,ou=DSA,ou=manuf,o=altissemiconductor.com,cn=mfg ldap suffix = ou=manuf,o=altissemiconductor.com,cn=mfg ldap group suffix = ou=Groups ldap user suffix = ou=Users...

Helo, We use a big fileserver running Linux/Samba as fileshare. We are facing performances problems for which we'd like some advise : Clients are OS2(LanManager) and windows 2000 reading and writing lots of files in the same directory on the fileshare. We currently have more than 80 000 files in the directory (files size is about 100 Bytes). Could you please advise us some Samba tuning

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, I got the following error synchronising between to servers : 2002/07/04 20:58:39 [68722] transfer interrupted (code 12) at token.c(255) Between other servers rsync is OK without any error. Is it a know bug ? I can't easily upgrade rsync because it's running on a server running 24h/24h 7/7. So before upgrading I need elements to explain the problem which occurs. Thank's for your

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

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.