Subject: Re: NFS to Solaris: Value too large for defined data type on 0 sized files
To: None <netbsd-help@netbsd.org>
From: Thorsten Frueauf <milano@zhadum.de>
List: netbsd-help
Date: 08/03/2000 22:38:43
Hello,

> That seems to work. I restarted the sun and it did work until now. what
> does that? Would someone add this to some online doc at netbsd.org?

This lets an NFS client and server accept times that are > Y2038. This
tunable is used in situations when the timestamp on a file is negative,
i.e. before 1970, and the user still wants to access these files.

> The other errors are gone, an now I have a new one:
> 
> fastcp: Can't set time on '/Net/alice/raid/Users/dave/projects/ebox/zooplus/Affiliate/Affiliate.woa/WebServerResources//box_grau_unten_kl.gif'.
> make: *** [wo-copy-global-resources] Error 255

Well, setting "nfs:nfs_32_time_ok" allows you to read the file, but its
still not possible to generate a file with that kind of timestamp.
I don't know what "fastcp" does, but I would suggest to just copy the
file without keeping the original timestamp information. Or touch the file
on the NFS server site. The other possibility would be to rewrite
"fastcp" as true 64bit application, but I don't know if this is an option in
your case.

Greets
      Thorsten