[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug#497514: coreutils: chmod, chown, and chgrp change ctime even wh
From: |
Paul Eggert |
Subject: |
Re: Bug#497514: coreutils: chmod, chown, and chgrp change ctime even when no change was necessary |
Date: |
Thu, 11 Sep 2008 10:56:34 -0700 |
User-agent: |
Gnus/5.101 (Gnus v5.10.10) Emacs/22.2 (gnu/linux) |
Erik Rossen <address@hidden> writes:
> And, if one wants to be REALLY pedantic, it looks like the file node is
> supposed to be changed each time. For example, here is an extract:
As I read the spec, chown and chgrp are explicitly required to make
the equivalent of a chown() call, which in turn is required to change
the ctime. However, chmod is not required to make the equivalent of a
chmod() call, and there is no requirement in the 'chmod' spec that it
change the ctime. So POSIX allows the optimization for the 'chmod'
command, but not for the 'chown' and 'chgrp' commands.
- Re: Bug#497514: coreutils: chmod, chown, and chgrp change ctime even when no change was necessary, Jim Meyering, 2008/09/02
- Re: Bug#497514: coreutils: chmod, chown, and chgrp change ctime even when no change was necessary, Erik Rossen, 2008/09/02
- Re: Bug#497514: coreutils: chmod, chown, and chgrp change ctime even when no change was necessary,
Paul Eggert <=
- Re: Bug#497514: coreutils: chmod, chown, and chgrp change ctime even when no change was necessary, Eric Blake, 2008/09/11
- Re: Bug#497514: coreutils: chmod, chown, and chgrp change ctime even when no change was necessary, Jim Meyering, 2008/09/12
- Re: Bug#497514: coreutils: chmod, chown, and chgrp change ctime even when no change was necessary, Michael Stone, 2008/09/12
- Re: Bug#497514: coreutils: chmod, chown, and chgrp change ctime even when no change was necessary, Jim Meyering, 2008/09/13