Date: Sat, 31 Jul 1999 10:22:19 -0400 From: Sergey Babkin <babkin@bellatlantic.net> To: Warner Losh <imp@village.org> Cc: "Brian F. Feldman" <green@FreeBSD.ORG>, "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, hackers@FreeBSD.ORG Subject: Re: So, back on the topic of enabling bpf in GENERIC... Message-ID: <37A3069B.819E8D69@bellatlantic.net> References: <37A25361.34799F96@bellatlantic.net> <Pine.BSF.4.10.9907301619280.6951-100000@janus.syracuse.net> <199907302342.RAA85088@harmony.village.org> <199907310241.UAA85677@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Warner Losh wrote: > > In message <37A25361.34799F96@bellatlantic.net> 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 majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37A3069B.819E8D69>