[EMAIL PROTECTED] said: >On Tue, 25 Jun 2002, at 8:45am, [EMAIL PROTECTED] wrote: >> ... you shouldn't allow NFS access to your mail spool ... > > Ever. NFS's history of piss-poor file locking means a shared mailspool is >a recipe for disaster in any kind of heterogeneous environment. It might >work if your favorite implementation does locking right, and everyone is >using that same implementation, but otherwise, forget it.
Well yeah. And NFS is inherently insecure. If you don't trust the environment, you shouldn't run it. MH's file format doesn't really need locking. Each new incoming message is a new file so you very rarely have more then one process modifying the same file. I *could* just run ssh & X to run exmh/nmh. But then I'd need galeon, ee, openoffice, etc on my firewall too. I have run an environment with an NFS shared mail spool w/ 100 users on Solaris 2.5.1. Most users were using mailtool or netscape or pine. I never had a problem, despite the theoretical (and real) issues with NFS file locking. Sometimes a 90% solution that exists is better then the 100% solution that is unattainable. >-- >Ben Scott <[EMAIL PROTECTED]> >| The opinions expressed in this message are those of the author and do not | >| necessarily represent the views or policy of any other person, entity or | >| organization. All information is provided without warranty of any kind. | > > >***************************************************************** >To unsubscribe from this list, send mail to [EMAIL PROTECTED] >with the text 'unsubscribe gnhlug' in the message body. >***************************************************************** > -- ------- Tom Buskey ***************************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *****************************************************************
