Can't reload `router.db` without web interface

[ytti]

Can't reload `router.db` without web interface

[ytti]

The web is by design only way to interact it with now. Only reason -web is in separate package is because you might want to run oxidized-script without running oxidized, and you still need oxidized for dependencies but oxidized-web brings many other dependencies not needed by oxidized-script.

I am open on what the proper way to interact with Oxidized should be

• HTTP
• POSIX MQ
• Domain socket
• Named pipe
• Signal
• Something else?

What ever it is, we shouldn't be duplicating work, so if HTTP is going to be needed anyhow, solution should be abstracted so that minimal amount of work is needed to maintain two ways.
Signals does not seem very appealing because limited amount of signals available.

[RichiH]

Signals are the default way, but limited if you want to do more complex stuff, agreed.

For the very specific, and common, case of "reload your list" it still seems to be the best thing to do, though.

If you feel like it, named pipe with text or JSON may be an option, but is likely overkill. You could use the same JSON interface for your web UI, though.

[fhibler]

Fixed in db165b5

kill -HUP 123 should work then

[RichiH]

Thanks!

[fhibler]

Just opened #79
Oxidized seems to die on HUP reload.

[ytti]

Fixed in 4908e39