search for: marc_jacobsen

Hi list, I am planning to deploy samba 2.2.6 on a two-node cluster running Tru64 UNIX 5.1A. Each node will be running an instance of samba providing different services, but I want the locks directory to be shared between them so that if one node goes down, the other can take over its services and still have correct information about open files etc. My question: Can the tdb's handle being

Hi, we found that the timestamp of files is not displayed correctly, since the time switched to summer time. The file server has the right time and under unix the "ls -l" shows the correct time, but under windows 1h is added (all files seems to live in the future). Any hint ? Bye, Peer _________________________________________________________ Max-Planck-Institut fuer Biogeochemie

Hello again (I hope it's not too much to have two questions in one day :), Currently I'm testing quota support on Linux system with kernel 2.4.18 + XFS 1.1 patch + Samba 2.2.7 (--with-quota compiled) and I went into one really unpleasant problem when accesing Samba share from Windows 2000 SP3 with Total commander 5.5. When user reach soft limit, then he'll get a warning message

Hello, I have SAMBA 2.0.4 up and running on HP-UX 11 with "security = domain". The workgroup, password server, password encryption, etc. are all set up correctly and it works great, if the client is part of the same domain. I am using an NT 4.0 Workstation with SP4 as my client, and an NT 4.0 Server is my PDC (also the "password server" on the SAMBA system of course). As I