On 2025-10-06 01:08, Guy Harris wrote:
I think the original intent in supporting it in the node operations was to
allow *NFS servers* to access it and return ESTALE
Ah, thanks, that pretty much explains it. So this wasn't intended for
general (non-root) use and it's out-of-place in localtime.c. I have
reverted the change in the development repository on GitHub.
At most, I think it means that, on some platforms, you won't be able to detect
the case wherein a version of the TZif file in question was removed and
replaced with a different one *that happened to get the same inode number as
the previous one* - but the code would presumably also be checking for the
modification and node-change time, which would presumably normally catch that
case.
Yes, we check st_ctim (node-change time), which should suffice on POSIX
platforms, since it changes whenever st_mtim (modification time) does.
