Hello! Do someone use Samba 3.0.2 in production on file server? When I tired to migrate our fileserver to 3.0 from 2.2.8a with only 200 (or 300, hmm, I don't remember ;-) ) users, with about a 40-50 users, which use old dos clipper based application, I had locking problems (someone can say that this was not locking problem, but I think so). Now I want to try migration to 3.0.2. But, may be somebody already did such thing. Oh, I forgot- OS is Linux, SLES8.
Frank John Bruzzaniti
2004-Feb-12 12:08 UTC
[Samba] samba 3.0.2 in production on file sever?
I haven't used 3.0.2 yet but we have been using 3.0.2 RC2 in production without a hitch on our main file and print server running fedora core 1. I found 3.0.1 too be a little too buggy but RC2 works fine as a domain member server with printing, ADS and winbind. On Thu, 2004-02-12 at 04:47, Dmitry Melekhov wrote:> Hello! > > Do someone use Samba 3.0.2 in production on file server? > When I tired to migrate our fileserver to 3.0 from 2.2.8a with only 200 (or > 300, hmm, I don't remember ;-) ) > users, with about a 40-50 users, which use old dos clipper based > application, I had locking problems > (someone can say that this was not locking problem, but I think so). > Now I want to try migration to 3.0.2. > But, may be somebody already did such thing. > Oh, I forgot- OS is Linux, SLES8. >
daniel.jarboe@custserv.com
2004-Feb-12 15:30 UTC
[Samba] samba 3.0.2 in production on file sever?
Hello Dmitry,> When I tired to migrate our fileserver to 3.0 from 2.2.8a with only200> (or > 300, hmm, I don't remember ;-) ) > users, with about a 40-50 users, which use old dos clipper based > application, I had locking problems > (someone can say that this was not locking problem, but I think so). > Now I want to try migration to 3.0.2. > But, may be somebody already did such thing. > Oh, I forgot- OS is Linux, SLES8.Was the 2.2.8a without problems also running on SLES8? What makes you suspect a locking problem? What architecture is this, and how did you build 3.0.0? Thanks, ~ Daniel ----------------------------------------------------------------------- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.