Date: Thu, 04 Mar 2021 15:08:02 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 241577] F_SETLK on NFS is not working Message-ID: <bug-241577-3630-eaGtjEOqS6@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-241577-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-241577-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241577 Rick Macklem <rmacklem@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rmacklem@FreeBSD.org --- Comment #2 from Rick Macklem <rmacklem@FreeBSD.org> --- Or use the "nolockd" mount option, which should work ok unless the locks need to be visible to other clients (which does not sound like it is the case here). Another alternative, if your NFS server supports it, is switching to NFSv4. Maybe a little more bothersome to configure, but does support file locking pretty well. (The rpc.lockd implements a crappy protocol called NLM, which can work ok, but should be avoided imho.) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241577-3630-eaGtjEOqS6>