Viewing the properties of a writable file on the server using Win2K or WinXP
file explorer corrupts the file's timestamp when running on Linux/Alpha. The
client sends a trans2 SET_FILE_BASIC_INFO command with all times set to
0xffffffffffffffff. Normally, this causes the timestamp conversion routine to
reject the timestamp as invalid, converting it to 0; however, it does this only
as a side-effect, and not because it recognizes 0xffffffffffffffff as a special
value. On most systems, this will result in a timestamp value that's outside of
the range (TIME_T_MAX,TIME_T_MIN) -- *except* on machines which support a 64-bit
signed time_t, such as Linux/Alpha. The fix is to recognize this special value
and convert it to 0 on all platforms.
Patch to follow.
Created attachment 17 [details]
one-liner patch to fix timestamps on Linux/Alpha
Tridge has applied this patch.
Steve, can you test and mark as validated?
confirmed, the patch committed to CVS looks correct.
*** Bug 1091 has been marked as a duplicate of this bug. ***
originally reported against 3.0aph24. Bugzilla spring cleaning.
Removing old alpha versions.