From owner-freebsd-questions@FreeBSD.ORG Sun Jun 13 20:16:46 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7700616A4CE for ; Sun, 13 Jun 2004 20:16:46 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id F260243D2F for ; Sun, 13 Jun 2004 20:16:45 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i5DKGfb6014491; Sun, 13 Jun 2004 15:16:41 -0500 (CDT) (envelope-from dan) Date: Sun, 13 Jun 2004 15:16:41 -0500 From: Dan Nelson To: Palle Girgensohn Message-ID: <20040613201640.GE94119@dan.emsphone.com> References: <1FDA476097EB5EBC0B3F23A3@palle.girgensohn.se> <20040613200046.GD94119@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: questions@freebsd.org Subject: Re: "unlocking" stale nfs? adding -t to running nfsd? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jun 2004 20:16:46 -0000 In the last episode (Jun 13), Palle Girgensohn said: > --On Sunday, June 13, 2004 15:00:47 -0500 Dan Nelson > wrote: > >In the last episode (Jun 13), Palle Girgensohn said: > >>I should really do this mount with tcp, of course, but found no way > >>to get a running nfsd to also start accepting tcp (nfsd runs with > >>"-n 6 -u", no -t). Is there a way to tell a running nfsd to start > >>accepting tcp connections? > > > >Just bounce nfsd after changing nfs_server_flags in rc.conf. > > bounce, you mean like kill -USR1 ? Surely, nfsd does not read > rc.conf, so kill -USR1 #pid && nfsd -t ...? Is that safe when the > server has active clients? In 5.x, you can run /etc/rc.d/nfsd restart, which does read rc.conf. In 4.x and earlier, you'll have to kill and restart it manually, like you wrote. Clients shouldn't notice anything except a short delay if they try to do something while nfsd is down on the server. -- Dan Nelson dnelson@allantgroup.com