-----BEGIN PGP SIGNED MESSAGE----- I understand that fcntl locks don't work over NFS, but apparently fcntl used to set errno to ENOLCK if you tried it, while now it sets it to EACCESS. That's apparently why the same code worked fine on slink. libPropList will work fine if it's not able to establish the lock, and it does check for that situation. But the change in libc's behavior broke the checks that libProbList uses. So I don't see how it can be libProbList's problem. Why did the libc behavior change? Who should be contacted regarding libc development questions like this?
noah On Sat, 13 Nov 1999, Havoc Pennington wrote: > > Hi, > > fcntl() locks don't work over NFS, unfortunately (well, I'm told they > "sort of" work in 2.2 kernels, but I wouldn't count on it). Even if they > work over NFS they may not work with other networked file systems or on > non-Linux systems. > > So the fix is actually complicated, libPropList needs to use a different > type of locking. You might want to ask the libPropList author about it. > > Havoc > > > > > 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 iQCVAwUBOC3ee4dCcpBjGWoFAQHIYwP9HXepEUJGN3NQwfP9pnPOM0KixanvKcYV 5TeQZpwQvokYqhEuxWGNzVNMvj5KiqvM56OVJqQ/s98LktS8dXjIpW/x8jwr3xNV gx09MBilpOFccVWzS0a+pGmccjkobQLY0a56/cBVHxRkFQN4dx8q6NgMwaONJMdH XSKzj9ac0pA= =TTju -----END PGP SIGNATURE-----
