Problems Re-Starting mountd

[Rick Macklem]

You could test the attached patch, which I think makes mountd
load new export entries from a file called /etc/exports.new
without deleting the exports already in place, when sent a
USR1 signal.

After applying the patch to mountd.c, rebuilding and replacing
it, you would:
- put new entries for file systems not yet exported in both
  /etc/exports and /etc/exports.new
# kill -USR1 <mountd's pid>
- delete /etc/exports.new
Don't send HUP to mountd for this case.

Very lightly tested, rick
ps: Sometimes it's faster to just code this stuff instead of
    discussing if/how it can be done;-)
pss: This patch isn't ready for head. If it is useful, it might
    make sense to add a new mountd option that specifies the
    name of the file (/etc/exports.new or ...), so that this
    capability isn't enabled by default.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: newexports.patch
Type: text/x-patch
Size: 3115 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20130108/1db08664/attachment.bin>