When we change the exportfs file on our FreeBSD 9.1 fileserver:
kill -HUP `cat /var/run/mountd.pid`
it kills the jobs on clients that have files open on the fileserver.
This is pretty inconvenient for users (and us). Is there a way around
this? We have noticed that a Linux fileserver can
2013-05-03 12:49, Daniel Feenberg skrev:
When we change the exportfs file on our FreeBSD 9.1 fileserver:
kill -HUP `cat /var/run/mountd.pid`
That seems a bit harsh, try /etc/rc.d/nfsd restart or
/etc/nfsserver restart.
it kills the jobs on clients that have files open on the
On Fri, May 03, 2013 at 02:08:26PM +0200, Bernt Hansson wrote:
2013-05-03 12:49, Daniel Feenberg skrev:
When we change the exportfs file on our FreeBSD 9.1 fileserver:
kill -HUP `cat /var/run/mountd.pid`
That seems a bit harsh, try /etc/rc.d/nfsd restart or
/etc/nfsserver restart.
On Fri, 3 May 2013, Graham Allan wrote:
On Fri, May 03, 2013 at 02:08:26PM +0200, Bernt Hansson wrote:
2013-05-03 12:49, Daniel Feenberg skrev:
When we change the exportfs file on our FreeBSD 9.1 fileserver:
kill -HUP `cat /var/run/mountd.pid`
That seems a bit harsh, try
Actually, changes to /etc/exports under FreeBSD take effect when you
either kill -HUP mountd.pid or /etc/rc.d/mountd reload|restart on the nfs
server, but both disrupt existing mounted shares on the nfs client.
What we are looking for is an equivalent of exportfs -r under Linux. Is
that
