public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-kernel@schottelius.org>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why is one sync() not enough?
Date: Wed, 15 Jun 2005 08:19:04 +0200	[thread overview]
Message-ID: <20050615061904.GJ1467@schottelius.org> (raw)
In-Reply-To: <9a87484905061408585c52f96b@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

Jesper Juhl [Tue, Jun 14, 2005 at 05:58:36PM +0200]:
> [sync twice, sync waits for sync]
> 
> I believe sync in recent Linux's actually waits for the data to be
> written and never returns early, so I don't think this is relevant any
> more - and everyone uses shutdown these days anyway. But go read the
> implementation of sync if you really want to know.

Thanks for the detailled instructions. I'll have a look at
the sync implementation to see how it really works.

Anyway: As I am writing an init-system, I also have to write a
shutdown procedure ;-)

Greetings,

Nico


-- 
Keep it simple & stupid, use what's available.
Please use pgp encryption: 8D0E 27A4 is my id.
http://nico.schotteli.us | http://linux.schottelius.org

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

  parent reply	other threads:[~2005-06-15  6:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14  9:41 Why is one sync() not enough? Nico Schottelius
2005-06-14 12:58 ` Martin Waitz
2005-06-14 15:58   ` Jesper Juhl
2005-06-14 18:36     ` Valdis.Kletnieks
2005-06-15  6:19     ` Nico Schottelius [this message]
2005-06-15  4:50 ` Andrew Morton
2005-06-15  3:39   ` jmerkey
2005-06-15  8:20   ` Bernd Eckenfels
2005-06-15 10:55   ` Nico Schottelius
2005-06-15 19:41     ` Andrew Morton
2005-06-15  8:17 ` Helge Hafting
2005-06-15  9:28   ` Denis Vlasenko
2005-06-15  9:43     ` Coywolf Qi Hunt

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=20050615061904.GJ1467@schottelius.org \
    --to=nico-kernel@schottelius.org \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.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