On Tue, 11 Apr 2017 16:41:16 -0600
"Theo de Raadt" wrote:
> > Note that I have noatime on this FS.
>
> Maybe we should remove this broken feature.
>
I would love to know what is broken about it, so I can investigate
this and disable it on my systems if it's too risky
On Tue, 11 Apr 2017 19:39:28 -0700
Philip Guenther wrote:
> The 'issue' is that he's changing the parent of a directory and that
> means it has to update the ".." link inside the directory, so it
> alters the directory contents and the mtime is thus updated.
That explains a
On Tue, Apr 11, 2017 at 6:53 PM, Bob Beck wrote:
>
>> Note that I have noatime on this FS.
>
> then turn that off, or understand that things will not behave as you expect
> them to with it on.
Nah, the noatime is a red herring, nicely smeared across the evidence
trail here.
> Note that I have noatime on this FS.
then turn that off, or understand that things will not behave as you expect
them to with it on.
Sorry I was copying this out from a VM, so I ended up typing it up
wrong here:
$ mkdir Foo
$ touch -t 2101 Foo
$ ls -dlT Foo
drwxr-xr-x 2 bob bob 512 Jan 1 00:00:00 2000 Foo
$ ls -dluT Foo
drwxr-xr-x 2 bob bob 512 Jan 1 00:00:00 2000 Foo
$ mkdir Bar
$ mv Foo Bar/
$ ls -dlT Bar/Foo
> Note that I have noatime on this FS.
Maybe we should remove this broken feature.
On Tue, 11 Apr 2017 16:54:29 +0200
Ingo Schwarze wrote:
> Hi,
>
> bytevolc...@safe-mail.net wrote on Fri, Apr 07, 2017 at 12:25:10PM
> +1000:
>
> > Although mv(1) will preserve atime and mtime for moved directories
> > if moved to a different file system, it doesn't preserve
Hi,
bytevolc...@safe-mail.net wrote on Fri, Apr 07, 2017 at 12:25:10PM +1000:
> Although mv(1) will preserve atime and mtime for moved directories if
> moved to a different file system, it doesn't preserve them when moved
> in the same file system.
Cannot reproduce.
$ mkdir Foo
$ touch