Warner Losh wrote:
> 
> In message <[EMAIL PROTECTED]> Sergey Babkin writes:
> : Disabling bpf it will break rarpd (and also rbootd but it is less
> : important). I think such a thing should be mentioned in documentation.
> 
> Not if they are started before the secure level is raised.

A problem is that rarpd does not understand the SIGHUP signal
to reload the configuration (rbootd does). So if the RARP table
needs to be modified then rarpd has to be restarted. I guess
that the easiest way to fix it would be to add SIGHUP support
to rarpd.

And I think it's still worth mentioning in the documentation, to 
caution the sysadmins from killing and restarting the daemons
dependent on bpf.

-SB


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to