Date: Fri, 13 Sep 2002 16:14:20 -0700 From: Kris Kennaway <kris@obsecurity.org> To: current@FreeBSD.org Subject: file locking problems with NFS Message-ID: <20020913231420.GA52963@xor.obsecurity.org>
next in thread | raw e-mail | index | archive | help
--9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm getting weird problems on my 5.0 system trying to lock access to files on an NFS volume (RedHat NFS server). For example, here is what happens when I try and vi a file on the NFS volume: 58532 vi CALL flock(0x3,0x6) 58532 vi NAMI "/var/run/lock" 58532 vi RET flock -1 errno 4 Interrupted system call 58532 vi PSIG SIGINT caught handler=3D0x804b340 mask=3D0x0 code=3D0= x0 58532 vi CALL sigreturn(0xbfbfef58) 58532 vi RET sigreturn JUSTRETURN =20 Note flock is being called with LOCK_NB|LOCK_EX, i.e. non-blocking; yet it blocks until I SIGINT it. I am running rpc.lockd on the client, and it appears to also be running on the server (I don't know if Redhat includes a working lock manager or if it fakes it like ours used to). Any ideas? Kris --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9gnFKWry0BWjoQKURAgH4AJ9CL2BiZkgX7wpn/JaZ5Mazn74kBgCeKOVQ suOgfMMEfnv23KH6t56RpE0= =7fgQ -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020913231420.GA52963>