Reload BridgeDB by sending it a SIGHUP signal.
...because the --reload switch doesn't work. It's supported but doesn't actually reload BridgeDB. Instead, when running bridgedb --reload, one starts a second process, which then dies because it cannot bind to the necessary ports (because the original BridgeDB instance is already bound).
This partially fixes bridgedb#40001 (closed).
