aboutsummaryrefslogtreecommitdiff
path: root/contrib/global/htags
diff options
context:
space:
mode:
authorPeter Wemm <peter@FreeBSD.org>1998-05-30 16:33:58 +0000
committerPeter Wemm <peter@FreeBSD.org>1998-05-30 16:33:58 +0000
commit7c1c33a7dd16e123fb836b48b7318eca0026d75e (patch)
tree4f808c23626fbcbe2da4ab45af795e14b7e43829 /contrib/global/htags
parent6edfc50c8e9d5097a2f5e82cc8a6d7b1de5f9bd3 (diff)
downloadsrc-7c1c33a7dd16e123fb836b48b7318eca0026d75e.tar.gz
src-7c1c33a7dd16e123fb836b48b7318eca0026d75e.zip
When using NFSv3, use the remote server's idea of the maximum file size
rather than assuming 2^64. It may not like files that big. :-) On the nfs server, calculate and report the max file size as the point that the block numbers in the cache would turn negative. (ie: 1099511627775 bytes (1TB)). One of the things I'm worried about however, is that directory offsets are really cookies on a NFSv3 server and can be rather large, especially when/if the server generates the opaque directory cookies by using a local filesystem offset in what comes out as the upper 32 bits of the 64 bit cookie. (a server is free to do this, it could save byte swapping depending on the native 64 bit byte order) Obtained from: NetBSD
Notes
Notes: svn path=/head/; revision=36473
Diffstat (limited to 'contrib/global/htags')
0 files changed, 0 insertions, 0 deletions