@timecop, yes, that would mean that, if you want to see output when executing asterisk "by hand", then you would have to reenable the console logging in the configuration file.
OK, that was a good point, and I'm not an asterisk expert so I have no idea whether "attaching to remote console" is a scenario that happens often or not. I confess I was taking apache2 as an example here: you have the logs under /var/logs/apache2, and even if you execute apache2 by hand you will still *not* see the log being output to stdout/stderr. In any case, I still think it's not a good idea to silence the stderr input in journalctl, so while I think the proposed patch makes sense, I would remove the "StandardError=null" line from it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909816 Title: asterisk spams console output to syslog due to systemd misconfiguration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1909816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
