Jose Luis Duran 16d39eadf7 blacklistd: Don't remove a ruleset if we have already added it ... The noted argument is wrong - if it's already been deleted then the id we have for it is invalid. Because we don't track deletions to the ruleset, working it out is problematic at best. Instead, if we have already added the rule treat it as a non-op. This is a valid use case because we might receive a burst of messages in the downstream application for the same address and process them one by one. It's not the job of the downstream application to track blacklistd state. Obtained from: 959b18a604		2022-10-12 15:47:44 -04:00
..
blacklistctl.8
blacklistctl.c	blacklistd: Fix usage for blacklistd/blacklistctl	2022-10-12 10:30:12 -04:00
blacklistd.8	blacklistd: Update documentation changes	2022-10-12 09:27:08 -04:00
blacklistd.c	blacklistd: Don't remove a ruleset if we have already added it	2022-10-12 15:47:44 -04:00
blacklistd.conf.5	blacklistd: Update documentation changes	2022-10-12 09:27:08 -04:00
conf.c	blacklistd: whitespace cleanup	2022-10-12 13:41:44 -04:00
conf.h
internal.c
internal.h
Makefile
run.c	blacklistd: whitespace cleanup	2022-10-12 13:41:44 -04:00
run.h
state.c
state.h
support.c	blacklistd: whitespace cleanup	2022-10-12 13:41:44 -04:00
support.h