Date: Mon, 25 Jul 2011 12:06:23 -0500 (CDT) From: Ryan Langseth <langseth@meridian-enviro.com> To: FreeBSD-gnats-submit@FreeBSD.org Subject: ports/159187: [patch] sysutils/am-utils patch to add nolockd to nfs mount options Message-ID: <201107251706.p6PH6NrF026390@betelgeuse.meridian-enviro.com> Resent-Message-ID: <201107251730.p6PHU8Eb004659@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 159187 >Category: ports >Synopsis: [patch] sysutils/am-utils patch to add nolockd to nfs mount options >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Jul 25 17:30:08 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Ryan Langseth >Release: FreeBSD 8.1-RELEASE-p2 i386 >Organization: Meridian Environmental Technology >Environment: System: FreeBSD betelgeuse.meridian-enviro.com 8.1-RELEASE-p2 FreeBSD 8.1-RELEASE-p2 #5: Mon Dec 20 12:50:48 CST 2010 root@beastie.meridian-enviro.com:/usr/obj/usr/src/sys/STANDARD.8.i386 i386 >Description: If lockd is not running on the nfs server, things like sqlite databases will not be accessible over the nfs share. Adding the nolockd option to amd opts will make amd add the nolockd option to the mount command for the nfs share, and will then fail down to lockfiles. This problem affects things like Firefox, Chromium when home directories are on remote filesystems. >How-To-Repeat: Attempt to lock a file on an amd auto mounted nfs filesystem when the nfs server does not have lockd running. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201107251706.p6PH6NrF026390>