Opened 9 years ago
Closed 8 years ago
Last modified 8 years ago
#12563 closed Patch - Bug Fix (Fixed)
systemd mythtv-backend.service file update to prevent double logging
Reported by: | Owned by: | Stuart Auchterlonie | |
---|---|---|---|
Priority: | minor | Milestone: | 0.28 |
Component: | Packaging | Version: | Master Head |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
the mythtv-backend.service (for deb) is missing a statement to prevent logging to console. Logs to console are logged to /var/log/syslog, and mythbackend syslogs are logged to /var/log/mythtv/mythbackend.log
Attachments (1)
Change History (7)
Changed 9 years ago by
Attachment: | patch-01.patch.txt added |
---|
comment:1 Changed 9 years ago by
comment:2 Changed 9 years ago by
ok, didn't know. The situation now (on Mythbuntu) is that loglines end up twice on disk, which is not good at all. So probably more a packaging thing than MythTV related.
comment:3 Changed 8 years ago by
Milestone: | unknown → 29.0 |
---|---|
Owner: | set to Stuart Auchterlonie |
Status: | new → accepted |
Version: | Unspecified → Master Head |
comment:4 Changed 8 years ago by
Status: | accepted → infoneeded |
---|
I believe this has already been taken care of in the unit file which is already in the packaging repository as it now include --quiet on the mythbackend command line
ExecStart=/usr/bin/mythbackend --quiet --syslog local7 $ADDITIONAL_ARGS
Charles can you comment?
comment:5 Changed 8 years ago by
Milestone: | 29.0 → 0.28 |
---|---|
Resolution: | → Fixed |
Status: | infoneeded → closed |
Upstream packaging committed --quiet to fix the issue, as discussed in the ubuntu bug tracker.
closing as fixed
There is the position that logging to syslog is the wrong way to go and that it is legacy thinking, and that instead console logging to/via journald is the way forward for systemd. However, I have no dog in the systemd discussion/fight on debian.