Tim Southerwood <ts@doc.ic.ac.uk> writes:
Now that's very interesting. I shall examine this in more detail. All our Solaris servers have the same setup and I didn't do it - so my initial thought was "Solaris must be weird"!
Do you have anything different in your 2.8 solaris server?
Good question. Not that I know of - for the test was conducted in a LAN that isn't mine, I've masked the IP addresses and hostnames:
Sun Microsystems Inc. SunOS 5.8 Generic February 2000 bash-2.05$ cat /etc/dfs/dfstab [...comments snipped...] share -F nfs -o rw=@XXX.XXX.XXX.XXX/26 /space share -F nfs -o ro=@XXX.XXX.XXX.XXX/26 /opt
bash-2.05$ uname -a SunOS somehost 5.8 Generic_117350-04 sun4u sparc SUNW,Ultra-5_10
Are your nlockmgrs running? All relevant patches installed? The machines I tested on have been fully patched up two days before the test -- "pgrep lockd" and "rpcinfo -p" on client and server should tell you.
At any rate, I don't think Solaris fcntl-style file locking is broken.
-- Matthias Andree
Encrypted mail welcome: my GnuPG key ID is 0x052E7D95 (PGP/MIME preferred)