Date: Sat, 7 Dec 2002 23:40:48 +0100 From: Philip Paeps <philip@paeps.cx> To: current@freebsd.org Subject: Re: I'm impressed, but ... Message-ID: <20021207224048.GG27267@juno.home.paeps.cx> In-Reply-To: <20021207221018.GA373@raggedclown.net> References: <20021125004934.GA604@juno.home.paeps.cx> <20021207194135.GD27267@juno.home.paeps.cx> <20021207221018.GA373@raggedclown.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2002-12-07 23:10:18 (+0100), Cliff Sarginson <cls@raggedclown.net> wrote: > On Sat, Dec 07, 2002 at 08:41:35PM +0100, Philip Paeps wrote: > > On 2002-11-25 01:49:34 (+0100), Philip Paeps <philip@paeps.cx> wrote: > > Perhaps someone can make sense of this? I'm happy I can read my mail now, > > without having to kick the power button every so often, but I'd prefer to > > store my mail here and have the mailserver write over NFS. (Mainly for > > speed reasons). > > I suspect file locks across NFS as a possible source of this kind of > problem. Locking is always a problem over NFS :-/ It's one of the reasons I'm using maildirs instead of normal happy mboxes. Theoretically - correct me if I'm wrong - file locks shouldn't matter with maildirs as once a file is written, there's not much chance of it having to be written again, let alone by more than one process? How would one verify that NFS locking is causing pain? There's some NFS debugging stuff in NOTES... I'm willing to try anything to help fix this :-) - Philip -- Philip Paeps Please don't CC me, I am philip@paeps.cx subscribed to the list. If you see a man approaching you with the obvious intent of doing you good, you should run for your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021207224048.GG27267>