Date: Sun, 13 Jun 2004 15:16:41 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Palle Girgensohn <girgen@pingpong.net> Cc: questions@freebsd.org Subject: Re: "unlocking" stale nfs? adding -t to running nfsd? Message-ID: <20040613201640.GE94119@dan.emsphone.com> In-Reply-To: <B62434E4BDE2A7885234F28C@rambutan.pingpong.net> References: <1FDA476097EB5EBC0B3F23A3@palle.girgensohn.se> <20040613200046.GD94119@dan.emsphone.com> <B62434E4BDE2A7885234F28C@rambutan.pingpong.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jun 13), Palle Girgensohn said: > --On Sunday, June 13, 2004 15:00:47 -0500 Dan Nelson > <dnelson@allantgroup.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040613201640.GE94119>