Gnus development mailing list
 help / color / mirror / Atom feed
From: Matthias Andree <matthias.andree@uni-dortmund.de>
Subject: Re: maildir in Gnus vs. clock corrections and PID recycling
Date: Mon, 20 Jan 2003 00:42:10 +0100	[thread overview]
Message-ID: <20030119234210.GA8374@merlin.emma.line.org> (raw)
In-Reply-To: <m3ptqsag09.fsf@multivac.cwru.edu>

Paul Jarc schrieb am Sonntag, den 19. Januar 2003:

> > The supposedly later http://cr.yp.to/proto/maildir.html refines the
> > documentation, and demands that the middle part does not recur within
> > one second, which is still insufficient given that a computer clock
> > might be stepped back,
> 
> Stepping a clock backwards produces so many problems that it is better
> to ignore those problems, run the clock monotonically, and find a
> different way to deal with any problems that stepping backwards was
> supposed to solve.

This would mean rebooting systems when the clocks are fast and cannot be
just slowed reasonably -- this cannot be expected, so applications must
be prepared to clocks being stepped backwards. It'd be fine with me if
the program would just complain, the ultime goal is avoiding EVER
overwriting a file.

> That sounds like a good idea.  As long as all maildir writers do that,
> readers (programs that move messages from new/ to cur/) won't have to
> be changed.  nnmaildir does deliver new messages to tmp/ sometimes, so
> I'll change that.  But the problem isn't likely to affect nnmaildir
> anyway, since Emacs is long-lived and nnmaildir is not likely to
> deliver new messages within 1 second of Emacs starting or exiting.

Agreed.

-- 
Matthias Andree



  reply	other threads:[~2003-01-19 23:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-19  0:57 Matthias Andree
2003-01-19 23:14 ` Paul Jarc
2003-01-19 23:42   ` Matthias Andree [this message]
2003-01-20  0:08     ` Paul Jarc
2003-01-20  0:40       ` Matthias Andree
2003-01-22 23:41   ` Paul Jarc
2003-01-23 12:33     ` Matthias Andree
2003-01-20  0:58 ` Paul Jarc

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=20030119234210.GA8374@merlin.emma.line.org \
    --to=matthias.andree@uni-dortmund.de \
    /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).