From owner-freebsd-questions Mon Sep 17 21:53:35 2001 Delivered-To: freebsd-questions@freebsd.org Received: from dell.dannyland.org (dsl092-007-150.sfo1.dsl.speakeasy.net [66.92.7.150]) by hub.freebsd.org (Postfix) with ESMTP id 4AAC537B40D for ; Mon, 17 Sep 2001 21:53:33 -0700 (PDT) Received: by dell.dannyland.org (Postfix, from userid 1001) id 4137C5CB0; Mon, 17 Sep 2001 21:54:36 -0700 (PDT) Date: Mon, 17 Sep 2001 21:54:36 -0700 From: dannyman To: Ted Mittelstaedt Cc: "Robert J. Collins" , Brian Whalen , questions@FreeBSD.ORG Subject: Re: redundant mail servers Message-ID: <20010917215436.V11099@toldme.com> References: <20010917161215.U11099@toldme.com> <004c01c13ffd$7b223640$1401a8c0@tedm.placo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <004c01c13ffd$7b223640$1401a8c0@tedm.placo.com>; from tedm@toybox.placo.com on Mon, Sep 17, 2001 at 09:50:46PM -0700 X-Loop: djhoward@uiuc.edu Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 17, 2001 at 09:50:46PM -0700, Ted Mittelstaedt wrote: > >If you really want reliable mbox file locking on x86 hardware, you > >might want to try Solaris x86. > > There's already mbox file locking in FreeBSD you don't need to go to > Solaris for that. The issue is that there is not file locking in NFS > under FreeBSD 4.X series. You don't want to trust a "production" system to -CURRENT, though. > And if Solaris is your idea of reliable mbox locking I'd hate to see what > you consider unreliable! We use Solaris ourselves and while it's locking > is adequate, I've had a few weird deadly embrace situations happen with it. > And that's WITHOUT using Network Flaying System! When was this? The Smart People I've talked to tout Solaris for NFS stuff ... -danny -- http://dannyman.toldme.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message