You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default the info messages about ACCEPT and CLOSE of this service are listed as errors in my systemd journal.
Which results in spamming me with log reports since there are many attempts in my honeypot.
I thought these are level 1 and the default stderrthreshold is 2.
The text was updated successfully, but these errors were encountered:
I am not sure what do you mean "listed as errors". They are "glog.V(1).Infof()".
If you mean they go to the stderr, and you don't like it, there are many command line options to control the log. I think the log will go to files by default, unless you set -alsologtostderr or -logtostderr. INFO, WARNING, ERROR should go to different files, if I remember correctly .
I use the systemD journal and the listed logs there are marked as error instead of info.
In the previous project they where listed as info.
I set now both cli arguments in the readme to restore the "old" behavior.
Now there is no log at all which is fine for me because the flood of error level log entries in my systemD journal stopped now.
By default the info messages about
ACCEPT
andCLOSE
of this service are listed as errors in my systemd journal.Which results in spamming me with log reports since there are many attempts in my honeypot.
I thought these are level 1 and the default
stderrthreshold
is 2.The text was updated successfully, but these errors were encountered: