Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:12210 comp.os.386bsd.misc:3104 Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!usc!elroy.jpl.nasa.gov!decwrl!amd!netcomsv!calcite!vjs From: vjs@calcite.rhyolite.com (Vernon Schryver) Subject: Re: Whats wrong with Linux networking ??? Message-ID: <CuACID.6EF@calcite.rhyolite.com> Organization: Rhyolite Software Date: Tue, 9 Aug 1994 20:49:24 GMT References: <31trcr$9n@euterpe.owl.de> <3256t1$rbn@ra.nrl.navy.mil> <327nj0$sfq@sundog.tiac.net> Lines: 23 In article <327nj0$sfq@sundog.tiac.net> bill@bhhome.ci.net (Bill Heiser) writes: > ... >However the *REAL* problem with LINUX NFS is that it does not currently do >any file locking. So you can run into some real problems if, for example, >you NFS-mount your mail spool directory from another machine and both machines >try to write to it. > >Someone in c.o.l.d. mentioned that he wanted to work on this but couldn't >find the specs for the NFS file-locking mechanism. I hope he (or someone) >does soon! ... NFS locking should be easy to implement, but many people have tried and failed. A lot of big bucks have lost on the NFS locking saga, not least by Sun Microsystems, Inc. Unless you have access to working source, "just say no" to NFS locking. Use POP or rsh or something else to avoid NFS accesses to your mail spool directory. Use some other network file system protocol. Or use some kind of out-of-band, application specific protocol. Vernon Schryver vjs@rhyolite.com