On 26/09/2026 10:27, Thomas Klausner wrote:
My first test was on tmpfs. I reproduced it with NetBSD's tools:
#!/bin/sh
touch a || fail=1
btime=$(stat -f %B a) || fail=1
atime=$(stat -f %a a) || fail=1
ctime=$(stat -f %c a) || fail=1
mtime=$(stat -f %m a) || fail=1
echo $btime $atime $ctime $mtime
Running this twice on tmpfs gives:
# ~/nbtest.sh
1790414618 1790414618 1790414618 1790414618
# ~/nbtest.sh
1790414618 1790414620 1790414618 1790414620
Does it happen on other file system types?
It's different on ffs:
# ./nbtest.sh
1790414514 1790414604 1790414604 1790414604
# ./nbtest.sh
1790414514 1790414611 1790414611 1790414611
So... is this a bug in tmpfs or usual variation?
That does look like a NetBSD tmpfs bug.
We should document that in gnulib at least.
thanks,
Padraig
