Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: "Fixing up" gnus - (how hard is this?). (was Re: (provide 'nnmaildir))
Date: 18 Oct 2000 16:29:56 -0400	[thread overview]
Message-ID: <m3og0hao4l.fsf@multivac.student.cwru.edu> (raw)
In-Reply-To: Rob Browning's message of "18 Oct 2000 15:07:15 -0500"

Rob Browning <rlb@cs.utexas.edu> writes:
> prj@po.cwru.edu (Paul Jarc) writes:
> > But use rename(), not link()/unlink(), for appropriate atomicity.
> 
> Well the tricks I know of were designed to make sure you DTRT (as much
> as possible anyway), even in the case where the files are on NFS
> mounted volumes, but I don't know if you want to worry about that, and
> it's possible that rename handles that already...

AFAIK, NFS handles rename correctly.  In the case of concurrent
readers, you definitely want rename, since it guarantees that when a
file exists with the new name, it will be replaced atomically, so
readers will always find one file or the other unde that name.

> > Hmm... nnmaildir's state files are non-Lisp text, parsed manually.
> > I suppose (read)ing Lisp expressions would probably be faster,
> > though.  I hadn't thought of that.
> 
> Might be a lot easier for you to handle code-wise too.

Yes, I imagine so.


paul



  reply	other threads:[~2000-10-18 20:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-17 16:00 Rob Browning
2000-10-17 20:29 ` "Fixing up" gnus - (how hard is this?) Paul Jarc
2000-10-17 22:53   ` Rob Browning
2000-10-17 20:51 ` "Fixing up" gnus - (how hard is this?). (was Re: (provide 'nnmaildir)) Simon Josefsson
2000-10-17 22:32   ` Rob Browning
2000-10-18 15:13     ` Paul Jarc
2000-10-18 20:07       ` Rob Browning
2000-10-18 20:29         ` Paul Jarc [this message]
2000-10-19  0:20           ` Rob Browning
2000-10-19 16:05             ` Paul Jarc
2000-10-19 23:29               ` Rob Browning
2000-10-20  0:03                 ` Paul Jarc
2000-10-20  9:21               ` Kai Großjohann
2000-10-20 15:27                 ` Paul Jarc
2000-10-20 21:08                   ` Kai Großjohann
2000-10-20 21:17                     ` Paul Jarc
2000-10-20 21:45                       ` Kai Großjohann

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=m3og0hao4l.fsf@multivac.student.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).