Hi Frank, thanks for your report.
On Friday 22 August 2008 17:47, Frank Doepper wrote:
> According to CHANGES the reloading of the config files via
> SIGHUP is supported since version 2.0.1, but /etc/init.d/arpalert still
> denies it.
reading the following changelog entry doesn't convince me, that sending SIGHUP
is resulting into a complete reload:
reload "white list", "black list", "authorizations"
and "oui.txt" when a sighup is received
Thierry: Can you please clarify, if sending SIGHUP is resulting into a
complete reload or just only reloading the mentioned parts of the
configuration?
Thanks and with kind regards, Jan.
--
Never write mail to <[EMAIL PROTECTED]>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d-- s+: a- C+++ UL++++ P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE
Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++
------END GEEK CODE BLOCK------
pgpC2ttU0ABgS.pgp
Description: PGP signature
