mirror of
https://github.com/evilsocket/opensnitch.git
synced 2025-03-04 16:44:46 +01:00
![]() Under heavy network traffic load, writing to a remote syslog fails with a timeout. Under this situation the connection didn't recover from that state, blocking other connections. To ensure that we continue working normally, as well as keep sending events to syslog: - Set a max timeout when writing to a remote syslog. - Restart the connection with the server, if there're more than 10 errors. With these fixes along with few other changes, writing to remote syslog is more reliable, it works as expected. We need to find the root cause of this behavior, and further test it (#638). |
||
---|---|---|
.. | ||
formats | ||
loggers | ||
log.go |