From: "Greg A. Woods" <woods@robohack.ca>
To: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: Re: [TUHS] reboot(2) system call
Date: Tue, 26 Jan 2021 22:01:12 -0800 [thread overview]
Message-ID: <m1l4dtA-0036xBC@more.local> (raw)
In-Reply-To: <CANCZdfosFGpBKw0wOx9nYgAWpeVNuRd-h6Nu5PLgZyyCuezZKA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
At Mon, 27 Jul 2020 12:57:59 -0600, Warner Losh <imp@bsdimp.com> wrote:
Subject: [TUHS] reboot(2) system call
>
> I've done some research for a friend about when the reboot() system call
> was added, and how it related to the sync, sync, sync dance.
>
> https://bsdimp.blogspot.com/2020/07/when-unix-learned-to-reboot2.html
>
> may be of interest. Please do let me know if I've gotten something wrong...
I've definitely experienced the second "sync" blocking until the first
was done. Once upon a time I remembered exactly why that happened, but
I no longer do.
The lore I was told at the time was that you alwasy ran three and that
it didn't matter if they were all on the same line with semicolons or
not because of the very fact that the second one would block.
The third one was just for superstitious good luck, and just in case
there was a process still running and writing to a filesystem.
--
Greg A. Woods <gwoods@acm.org>
Kelowna, BC +1 250 762-7675 RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com> Avoncote Farms <woods@avoncote.ca>
[-- Attachment #2: OpenPGP Digital Signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2021-01-27 6:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 18:57 Warner Losh
2020-07-28 0:36 ` Clem Cole
2020-07-28 4:06 ` Dave Horsfall
2020-07-28 16:35 ` Win Treese
2020-07-28 13:11 ` Jaap Akkerhuis
2021-01-27 6:01 ` Greg A. Woods [this message]
2021-01-30 22:27 ` Dave Horsfall
2021-01-30 22:31 ` Larry McVoy
2021-01-30 22:37 ` Warner Losh
2021-02-02 2:20 ` Greg A. Woods
2021-02-02 2:30 ` Warner Losh
2021-02-02 20:30 ` Greg A. Woods
2021-02-02 3:35 ` Dave Horsfall
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=m1l4dtA-0036xBC@more.local \
--to=woods@robohack.ca \
--cc=tuhs@tuhs.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).