[OpenAFS-devel] Solaris-8/64-bit problem with mtime = Jan 1 1970

[Derek Atkins]

Are both machines in the same Time Zone?  It looks like the machine
creating the file (remember, touch creates the file in the LOCAL
timezone, but stores the information in GMT).  This means that the
earliest time value you can store is 0000, 1 Jan 1970 GMT.  Assuming
you are NOT in GMT, then trying to store 197001010000 could cause a
problem, especially if you are east of GMT.

It's possible that you are storing a negative time value for that
first hour, and the negative value is being really confusing to the
64-bit machine.

-derek

Ole Benner <olb@kom.auc.dk> writes:

> Hi,
> 
> I have just discovered a problem on our OpenAFS client on
> Solaris-8/64bit. If I make a file on another platform with date "Jan 1
> 1970" and I try to stat it on Sol-8 I get this error:
> 
> On Linux w/ OpenAFS 1.0.4:
> --------------------------
> olb@bsa:[olb]$ touch -t 197001010000 test 
> olb@bsa:[olb]$ ls -l test
> -rw-rw-r--    1 olb      olb             0 Jan  1  1970 test
> 
> On Solaris-8/64bit with OpenAFS 1.0.4:
> --------------------------------------
> olb@ara:[olb]$ ls -l test 
> test: Value too large for defined data type
> 
> On Solaris-8/32bit there is no problem. A time value up to 197001010059
> failes on Sol-8/64bit and from 197001010100 and forward it is all right.
> 
> Has anyone alse seen that ?
> 
> Regards
> 
> Ole Benner
> System administrator
> Aalborg University
> IES, KOM-dept.
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord@MIT.EDU                        PGP key available