dynamically read rulefile feature

[nil0x42]

Hi!
It will be interesting to be able to tell glider reload rulefile without having to kill the process and run it again.

Like apache and many daemons do when you send a specific signal (SIGUSR1?)

Currently i have to kill & re-launch glider each time my rulefile changes, which also stops triggering packets

[soffchen]

Another advantage: reload rule file without flushing internal domain->ip map.

When glider restarts, which makes domain->ip map flushed, clients' dns doesn't update in time, all domain based rules get failed.

[sbkg0002]

Anyone found a solution on how to do this?

[wiwiwa]

Glider should not flush ipset when it is killed.

After glider exits and ipset is flushed, iptables will not forward packets to glider. Client dns cache has to be flushed.

[AsharLohmar]

This would be a "nice to have feature"
I'm using glider in a mix with different VPN clients, each in it's own docker container, in order to access different networks. I have a "main container" with only glider and a bunch of rule files, one for each "VPN container".
Every now and then I find my self in the need to add some new IP, CIDR or domain to the rule file of some VPN, so, in order to use this new rule, I have to restart this "main container" and by doing so... I'm killing all the existing "active connections" (mostly ssh sessions and/or tunnels).