From owner-freebsd-hackers Mon Oct 19 06:26:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA04570 for freebsd-hackers-outgoing; Mon, 19 Oct 1998 06:26:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from animaniacs.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA04565 for ; Mon, 19 Oct 1998 06:26:11 -0700 (PDT) (envelope-from jamie@itribe.net) Received: from localhost (jamie@localhost) by animaniacs.itribe.net (950413.SGI.8.6.12/950213.SGI.AUTOCF) via SMTP id JAA08764; Mon, 19 Oct 1998 09:25:24 -0400 Date: Mon, 19 Oct 1998 09:25:24 -0400 (EDT) From: Jamie Bowden To: Peter Jeremy cc: hackers@FreeBSD.ORG Subject: Re: softupdates and sync In-Reply-To: <98Oct19.070445est.40346@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Oct 1998, Peter Jeremy wrote: > On Sat, 17 Oct 1998 15:56:17 -0600, Warner Losh wrote: > >I guess I'm not making myself clear. Why doesn't sync(1) flush these > >things to disk? > sync(8) just calls sync(2). sync(2) just starts the buffer flush - it > does not wait for the flush to complete. This has always been true > and is the origin of the `type sync 3 times before halting system' > mantra. This mantra has never made any sense to me. The process of halting the system is unmounting filesystems, which will force syncing before umount happens. I have never bothered to manually sync a filesystem prior to a shutdown, reboot, or halt command. Jamie Bowden -- Systems Administrator, iTRiBE.net If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message