Re: Mysterious atime changes

From: Christian Weisgerber <naddy_at_mips.inka.de>
Date: Wed, 23 Feb 2022 15:26:08 UTC
Jon Schneider:

> A problem came up with Solidworks whinging about clocks. Like so many 
> error messages the real problem was something else specifically atimes 
> of files getting set to Jan 19 03:14:07 2038 and this happens in front 
> of my eyes on open files.

That is not a random time.  If that's UTC, then it corresponds
exactly to a time_t value of 0x7fffffff, i.e., INT_MAX.

(I have no idea what could cause this.)

-- 
Christian "naddy" Weisgerber                          naddy@mips.inka.de