All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@valinux.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Andrew McNamara <andrewm@connect.com.au>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	tytso@valinux.com, linux-kernel@vger.kernel.org
Subject: Re: Ext2, fsync() and MTA's?
Date: Mon, 21 May 2001 18:04:05 -0400	[thread overview]
Message-ID: <20010521180405.D495@think.thunk.org> (raw)
In-Reply-To: <E14ya9b-0004Bc-00@the-village.bc.nu> <20010512145338.0D3D6285BF@wawura.off.connect.com.au> <20010521184758.B24682@redhat.com>
In-Reply-To: <20010521184758.B24682@redhat.com>; from sct@redhat.com on Mon, May 21, 2001 at 06:47:58PM +0100

On Mon, May 21, 2001 at 06:47:58PM +0100, Stephen C. Tweedie wrote:
>
> No --- the old BSDs were safe because their directory operations were
> fully synchronous so they *never* needed to be sync'ed manually.
> According to SuS, an application relying on sync directory updates is
> buggy, because SuS simply makes no such guarantees.
> 
> Just set chattr +S on the spool dir.  That's what the flag is for.
> The biggest problem with that is that it propagates to subdirectories
> and files --- would a version of the flag which applied only to
> directories be a help here?
> 

That's probably the right thing to add.

						- Ted

  reply	other threads:[~2001-05-21 22:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-12 11:50 Ext2, fsync() and MTA's? Andrew McNamara
2001-05-12 14:13 ` Alan Cox
2001-05-12 14:53   ` Andrew McNamara
2001-05-12 15:20     ` Theodore Tso
2001-05-21 17:47     ` Stephen C. Tweedie
2001-05-21 22:04       ` Theodore Tso [this message]
2001-05-22 15:50         ` Oliver Xymoron
2001-05-22 16:48           ` Stephen C. Tweedie
2001-05-22 16:54             ` Oliver Xymoron
2001-05-22 16:57               ` Stephen C. Tweedie
2001-05-24  1:48       ` Marco d'Itri
2001-05-21 17:41   ` Stephen C. Tweedie

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=20010521180405.D495@think.thunk.org \
    --to=tytso@valinux.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrewm@connect.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.