Date: Wed, 11 Jan 2006 15:59:53 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: Ceri Davies <ceri@submonkey.net> Cc: freebsd-hackers@freebsd.org, Ahnjoan Amous <ahnjoan@gmail.com> Subject: Re: setfacl file modification time Message-ID: <20060111155348.J28748@fledge.watson.org> In-Reply-To: <7E919BA5-DF54-445D-98CA-E57E32B60892@submonkey.net> References: <5e575c8a0601051043r46ccfea1s352a5ea8ea7010a1@mail.gmail.com> <7E919BA5-DF54-445D-98CA-E57E32B60892@submonkey.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060111155348.J28748>