• Martin Blix Grydeland's avatar
    Only set new lurker destination ban if we already had one. · 93d80501
    Martin Blix Grydeland authored
    Without this we could start running ban_lurker_test_ban with an empty
    list of bans to test, causing a lot of unnecessary ban and oh mutex
    contention on every ban lurker invocation until the REQ ban triggering
    it is gone.
    
    Also don't call ban_lurker_test_ban when our destination ban is the
    same as the one being tested. This would be wasted work.
    
    Adjust the c00049.vtc test case for the bans now not being
    unnecessarily tested.
    93d80501
Name
Last commit
Last update
bin Loading commit data...
doc Loading commit data...
etc Loading commit data...
include Loading commit data...
lib Loading commit data...
m4 Loading commit data...
man Loading commit data...
.gitignore Loading commit data...
.travis.yml Loading commit data...
CONTRIBUTING Loading commit data...
ChangeLog Loading commit data...
INSTALL Loading commit data...
LICENSE Loading commit data...
Makefile.am Loading commit data...
Makefile.inc.phk Loading commit data...
Makefile.phk Loading commit data...
README Loading commit data...
README.Packaging Loading commit data...
autogen.des Loading commit data...
autogen.sh Loading commit data...
config.phk Loading commit data...
configure.ac Loading commit data...
flint.lnt Loading commit data...
varnish.m4 Loading commit data...
varnishapi-uninstalled.pc.in Loading commit data...
varnishapi.pc.in Loading commit data...