From owner-freebsd-bugs Wed Mar 22 08:59:43 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA09106 for bugs-outgoing; Wed, 22 Mar 1995 08:59:43 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA09096 for ; Wed, 22 Mar 1995 08:59:42 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA10757; Wed, 22 Mar 95 09:53:05 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9503221653.AA10757@cs.weber.edu> Subject: Re: Changed information for PR kern/260 To: bde@zeta.org.au (Bruce Evans) Date: Wed, 22 Mar 95 9:53:04 MST Cc: bde@zeta.org.au, davidg@Root.COM, freebsd-bugs@freefall.cdrom.com In-Reply-To: <199503221119.VAA11435@godzilla.zeta.org.au> from "Bruce Evans" at Mar 22, 95 09:19:05 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > > Kirk thinks utimes() is required by POSIX to be synchronous. > > It only requires that utime() sets the atime and mtime and marks the > ctime for update. I think the first requirement is satisfied by > overriding any existing marks for update. Then utime() acts as if > it set the times (unless the system crashes, and POSIX can't specify > that system crashes don't lose information). > > Similarly, chmod() and chmod() have to change the mode immediately, > but they can't be required to commit the change to eternally > warranteed media. Couldn't have said it better myself. The actual wording is "marked for update". Using the times (which only have a 1 second resoloution anyway) as an IPC facility is plain silly. If an update notification is needed, it should be as a result of some mechanism other than polling the date. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.