Jakesta13
commented
5 months ago I made an override edit to the service and it seems to have silenced the output. Be careful using Sudo!
sudo systemctl edit snap.duckpowered.actual-service.service- Then add the following lines after first 2 comments:
[Service]StandardOutput=null - run
sudo systemctl restart snap.duckpowered.actual-service.service - Then I ran
sudo systemctl daemon-reloadfor good measure.
I also added this to the rsyslog.config file, not sure if it actually works but just in case: Be careful using Sudo!
sudo nano /etc/rsyslog.conf- add the following (i placed at the bottom of the file):
if $programname contains 'duckpowered' then stop - run
sudo systemctl restart syslog.socket rsyslog.service - then I ran
sudo systemctl daemon-reload
the last command might not be needed, but I kept methodical while trying to silence this log spam
Also note there might be a better way to go about it, I personally was throwing stuff at the wall until it stuck.
For context I'm using a CM4 in a uConsole/Clockwork build (actually, writing this comment with it)
Hello. My syslog is cluttered by these entries every second. Is it possible to get rid off it?
dub 15 12:06:48 Tablet4 duckpowered.actual-service[