Very Computer

by **Ian G Batt** » Sat, 18 Feb 1995 00:37:54

Why did no-one tell me? Why wasn't it mentioned?
nfs_do_symlink_cache is set to 1 by default, and boot-and-login yields
about 3 readlink operations as reported by nfsstat -c. Set it to 0 (or
use 2.3) and it takes about 70 here (we use amd, which means that a lot
of readlinks are local to the machine, but are readlinks none the less).
Symlinks have gone back to the server since NFS has been around, and at
last it's been fixed!

ian

by **Jim Dav** » Sat, 18 Feb 1995 04:03:27

:Why did no-one tell me? Why wasn't it mentioned?
:nfs_do_symlink_cache is set to 1 by default, and boot-and-login yields
:about 3 readlink operations as reported by nfsstat -c. Set it to 0 (or
:use 2.3) and it takes about 70 here (we use amd, which means that a lot
:of readlinks are local to the machine, but are readlinks none the less).
:Symlinks have gone back to the server since NFS has been around, and at
:last it's been fixed!

I don't use amd, but according to traffic on the amd-workers mailing
list, that symlink caching will cause trouble unless you have the
current, upl90, release (ftp://ftp.cs.columbia.edu/pub/amd).
Otherwise, you can disable caching with 'set nfs:nfs_do_symlink_cache= 0'
in /etc/system, but it does seem a shame to have to disable such
a nice feature...

Very Computer

2.4 gets symlink cache!

2.4 gets symlink cache!

2.4 gets symlink cache!