[request] ability to turn off logs completely

[atesin]

i suffer for this issue: #54

i tried castspornsorskip for just 1 day, then my home server crashes, i hardly went to check and realized my disk has filled up with log messages like:

2023/12/11 21:44:33 ERROR Failed to discover devices. error="unable to create new zeroconf resolver: listen udp6 [ff02::]:5353: socket: address family not supported by protocol"

messages log so often than even with 1sec running, screen fulls and i cant scroll up to beginning with journalctl -fe-u castspornsorskip

i would like a way to suppress at all or filter or redirect log messages, as the lowest log level is error and these are precisely the level of these messages so cant be skipped

[gabe565]

@atesin Hmm you're right that it would be nice to suppress these messages. I should be able to add a none log level which would disable all logs! Let me investigate.

[gabe565]

@atesin Ok, I added a none log level which will be in v0.8.1, but I believe the zeroconf error will also be resolved in this release!

[atesin]

@atesin Hmm you're right that it would be nice to suppress these messages. I should be able to add a none log level which would disable all logs! Let me investigate.

that can alredy be done in systemd unit file: StandardError=null ... i wished a log filter option according a pattern, like rsyslog did.... too bad it seems that currently systemd doesnt work with rsyslog since a while, i did it before :/ (i.e. dropped StandardError=syslog)

in rsyslog log filters can be defined in configuration file according a process name, a message pattern, a facility, a log level, etc ...

if you or somebody discover how to effectivelly make systemd journal pass log messages to rsyslog to make a granular filter instead would be great, and you were not reinventing the wheel and use a standard way to do it that can be applied to any process

[atesin]

OR...

raise severity of these messages, so it can be filtered when using error level severity

or...

set more severity levels to allow more fine-gained log filters, based on this = https://en.wikipedia.org/wiki/Syslog#Severity_level

---

i regret that... if some actual error is in progress the right action to do is to correct it, not to silence it... that is logs are for