#18 SIGUSR1 to reload configuration

[Florian Sager]

Hi,

as we already discussed on the mailing list it would be helpful if dkim-filter could accept the signal SIGUSR1 to reload its configuration.

(Citing Murray S. Kucherawy, SIGHUP is currently intercepted by libmilter, not by code in dkim-filter itself. libmilter interprets it as a shutdown signal. Therefore SIGHUP cannot be used).

Thanks a lot,
Flo

[Anonymous]

Logged In: YES
user_id=1048957
Originator: NO

I'm beginning to design a solution to this request now. Hopefully I can provide this in 2.5.0. If you're eager to try it, you might want to sign up for the beta mailing list to be notified when beta releases start since 2.5.0 may have a long beta period.

[Anonymous]

Logged In: YES
user_id=1048957
Originator: NO

If you could pick a set of things to be reloaded (rather than "all of it") on signal, what would they be?

I ask because some things are tougher to arrange to reload than others. I might be able to do a first release of 2.5.0 that reloads only commonly-changed things, and then try to incorporate the rest later.

It's also possible that I will code it such that command line arguments are never re-read and only the configuration file is reloaded on a reload signal.

[Florian Sager]

Logged In: YES
user_id=701706
Originator: YES

At time DKIM Connector modifies entries in the files that are referenced by the following config-directives:

- Domain
- KeyList
- ExternalIgnoreList
- InternalHosts

I think the entries in these files have a more dynamic characteristics than the other settings in the config file. Our DKIM Connector requirements will be satisfied with reloading these external files in the first step. Thanks a lot!

[Anonymous]

Logged In: YES
user_id=1048957
Originator: NO

Done for 2.5.0, now released.