-----BEGIN PGP SIGNED MESSAGE----- On Mon, 15 Nov 1999, Marco d'Itri wrote:
> >WPrefs, and I was able to save it. So, it would seem that this is a > >problem with the errno value that is set from fcntl when it tries to > >create a lock on an NFS mounted file. Can anybody more knowledgeable > You are using a 2.2 kernel on the client and a 2.0 kernel on the server. > You don't have fcntl locking available so you should mount the file > system with -o nolock. Umm, no, that's not the case. I'm running 2.2 on both machines involved. Remember, this works fine when the client is a slink system with kernel 2.2.11, but not a potato system with 2.2.11. According to the documentation for fcntl(), it sets errno to ENOLCK when you try to set a lock on an NFS mounted file. This is not the behavior I am getting. It is setting errno to EACCES. This looks like a bug to me. I suspect glibc 2.1, because the same kernel works with glibc2.0, but not 2.1. The environment is the same in both cases, the client code is the same. The only difference is the glibc version. noah PGP Public Key available at http://www.morgul.net/~frodo/mail.html or by `finger -l [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: 2.6.3a Charset: noconv iQCVAwUBODAmCIdCcpBjGWoFAQE3LAP+OzNPsGF21xj8ErzHHPwAQsJNGxAvw7+y 1wZtLyfAuqF8WV7Tnhyvwv1RmsfrF1y7bB7WLiAqgZgd63+HqkecRkt7olaQpjiz JkHTxkK2BwohLlx7kJ8TWlpQrShMzvoR1KkrhcEg7T/lo6NGhlK6sJhcqa6CtMPQ XIV4PGQgCzo= =mbDu -----END PGP SIGNATURE-----