Feature #1290
openhandle SIGHUP signal
Description
Hello,
it would be nice to make Suricata to handle SIGHUP signal in a way that it would:
- reopen log files
- reopen unix socket
- reread configuration file
Currently if a unix socket is created after suricata starts, I must restart suricata in order to connect to socket.
If you implement it,
I could send SIGHUP (or other) signal to suricata every time when socket is created so it can reconnect successfully.
Kind regards,
Dariusz Binkul
Updated by Jason Ish over 9 years ago
In 2.0.4 a SIGHUP will re-open all the log files (zeroing them in doing so, on the assumption that a tool like logrotate has moved them out). I believe a SIGUSR2 will re-read the configuration.
I don't know enough about the unix socket to know if its a good idea to re-open it as part of the SIGHUP. Why does it need re-opening?
Updated by Dariusz Binkul over 9 years ago
Hello,
like I said. If a unix socket is created after suricata starts, I must restart suricata in order to connect to socket.
This is a problem, because you must config your system start scripts to check if a service that provides socket is init before suricata starts.
Another thing is that restart of a service that provide socket must be followed by a suricata restart.
If suricata could reopen unix socket, then suricata and socket provider(service) could work independently.
Kind regards,
Dariusz Binkul
Jason Ish wrote:
In 2.0.4 a SIGHUP will re-open all the log files (zeroing them in doing so, on the assumption that a tool like logrotate has moved them out). I believe a SIGUSR2 will re-read the configuration.
I don't know enough about the unix socket to know if its a good idea to re-open it as part of the SIGHUP. Why does it need re-opening?
Updated by Andreas Herz over 8 years ago
- Assignee set to OISF Dev
- Target version set to TBD
Updated by Victor Julien over 5 years ago
- Assignee changed from OISF Dev to Anonymous
So HUP would be like USR2, except it would handle socket reconnects as well?