Date: Mon, 27 Dec 1999 14:28:18 +0100 (CET) From: Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de> To: freebsd-questions@FreeBSD.ORG Subject: Re: How to I tell nfsd that /etc/exports has changed? Message-ID: <199912271328.OAA21065@dorifer.heim3.tu-clausthal.de>
next in thread | raw e-mail | index | archive | help
Alexey N. Dokuchaev wrote in list.freebsd-questions:
> On Sun, 26 Dec 1999, Oliver Fromme wrote:
> >
> > kill -HUP $(cat /var/run/mountd.pid)
> >
> > After that, you should do "tail /var/log/messages" to see
> > whether there were any problems with your /etc/exports file.
BTW, all of this is explained in the mountd(8) manpage. Please
read it.
> Well, it seems that I can simply rerun mountd, and it will reread
> /etc/exports -- just about the same effect as HUPing it.
>
> Any confirmations?
No. It will just start another copy of the mountd process,
leaving the old one hanging around. Sending a SIGHUP to the
daemon (using its PID file) is the "canonical" and most
portable way to let it re-read its config file. This works
for many other daemons, too.
Regards
Oliver
--
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de)
"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
(Terry Pratchett)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912271328.OAA21065>