From: Chris Richards <cjr@netpliance.net>
Cc: ding@gnus.org
Subject: Re: mbox as changed on disk, really edit?
Date: 29 Feb 2000 07:56:59 -0600 [thread overview]
Message-ID: <6ehfesun6c.fsf@sloth.netpliance.net> (raw)
In-Reply-To: Ulf Rompe's message of "29 Feb 2000 10:31:25 +0100"
Hrm. Close. My home directory *is* mounted via NFS, but the ~/Mail/
directory (on NFS) is a symlink back to /users/chrisr/Mail which is
local. The latter path is not exported--in other words, I can access
~/Mail/ only when I am on my Linux box.
I mainly did this thinking I would see an improvement in speed on
large nnfolders because the files are stored locally.
Cheers,
cjr
Ulf Rompe <Ulf.Rompe@icem.de> writes:
> Chris Richards <cjr@netpliance.net> writes:
>
> > I occassionaly get this message when I want to leave my buffer via
> > 'q'. I only read from $MAIL and no other process writes to
> > ~/Mail/mbox.
>
> Maybe your home directory is mounted via NFS and the client / server
> clocks are not synchronized?
>
> [x] ulf
prev parent reply other threads:[~2000-02-29 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-28 23:56 Chris Richards
2000-02-29 9:31 ` Ulf Rompe
2000-02-29 13:56 ` Chris Richards [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6ehfesun6c.fsf@sloth.netpliance.net \
--to=cjr@netpliance.net \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).