From owner-freebsd-bugs@FreeBSD.ORG Fri Feb 17 11:10:10 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCDB316A420 for ; Fri, 17 Feb 2006 11:10:10 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5449943D46 for ; Fri, 17 Feb 2006 11:10:10 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k1HBAAXf011890 for ; Fri, 17 Feb 2006 11:10:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k1HBAA9a011889; Fri, 17 Feb 2006 11:10:10 GMT (envelope-from gnats) Date: Fri, 17 Feb 2006 11:10:10 GMT Message-Id: <200602171110.k1HBAA9a011889@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: craig@backfire.ca Cc: Subject: Re: kern/91679: Re: setfacl file modification time X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: craig@backfire.ca List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Feb 2006 11:10:11 -0000 The following reply was made to PR kern/91679; it has been noted by GNATS. From: craig@backfire.ca To: bug-followup@FreeBSD.org Cc: rwatson@FreeBSD.org Subject: Re: kern/91679: Re: setfacl file modification time Date: Fri, 17 Feb 2006 06:04:27 -0500 > On Thu, 5 Jan 2006, Ceri Davies wrote: > > > On 5 Jan 2006, at 18:43, Ahnjoan Amous wrote: > > > >> In 5.2.1-RELEASE, setfacl updates the modification time of the file > >> when acls are changed. I haven't been able to find any complaints > >> about this behavior, is this something folks on the list would expect > >> when using setfacl? If so, does anyone know a work around? > > > > PR 76818 is open for this issue, but there is no progress logged at present. > > This likely occurs because EA writes modify the last modification timestamp. > I can imagine a couple of possible avenues to explore in fixing it, including: > > (1) Make system name space EA writes not update the modification time. > > (2) Add a flag to allow EA writes to be marked as not updating the > modification time. > > It could be POSIX.1e has something to say about time stamp modifications for > setfacl; personally I'd expect it to match the behavior of chmod. And I > believe chmod doesn't update the time stamp. > > Robert N M Watson I have not read the POSIX specification on this issue, nor do I have any authority on this matter, but I feel strongly that a file's mtime should not ever be changed by any filesystem utility, with the clear exception of /usr/bin/touch and perhaps others. If the POSIX spec requires that the mtime be changed during what is essentially a change to the file's metadata, I suggest that FreeBSD should diverge from the standard and document it accordingly. Cheers, -Craig Reyenga