Date: Mon, 30 Jun 1997 19:50:58 -0700 (PDT) From: Tom Samplonius <tom@sdf.com> To: Terry Lambert <terry@lambert.org> Cc: chuckr@glue.umd.edu, lmcsato@lmc.ericsson.se, freebsd-hackers@freebsd.org Subject: Re: NFS V3 is it stable? Message-ID: <Pine.BSF.3.95q.970630194523.16592A-100000@misery.sdf.com> In-Reply-To: <199707010018.RAA10515@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 30 Jun 1997, Terry Lambert wrote: > > I've had sites report that even going Solaris to Solaris using the > > Solaris propietary lockd stuff, they still can get trashed mailboxes. > > Locking of any kind over NFS just isn't reliable. > > This is only true if your NFS violates the NFS write guarantees, > which SVR4 and Solaris do, by default. Turn off write gathering > and write caching (the "adb" commands are listed in the Network > Administration Manual) and the problem will go away. So you make a trade reliable locking for performance? I'd take performance any day, and just forget about exporting mailboxes. ... > > Use IMAP as an alternative. Set up your mail server as a IMAP server, > > and use Pine, Simeon (www.esys.ca), or Netscape 4 on your clients. > > Netscape is a known rogue client. Among other things, it does not > cache the correct seperator character on a per "#xxx" namespace > escape. So if you were reading news in "#news" (seperator "."), > and went to create a new mail folder, it wouldn't use "/" as the > component seperator when communicating the new forlder path to the > server. Works with the Cyrus server, which is all I care about. I don't think the imap spec hides enougth server implementation details, which makes clients overly complex. > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.970630194523.16592A-100000>