Summary: | sys-libs/gpm-1.20.7-r4 systemd complains about an obsolete standard output type in the unite file | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Julien Delquié <julien.dlq> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | jstein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Julien Delquié
2022-08-07 06:21:18 UTC
I do not understand this report. * please set LANG=C * write exactly how to reproduce and what the bug is * if you have logs, please attach them and reopen the ticket I will try this, when I have time. I'm sorry, I forgot a line just before the second line of my original post, this was a log from « journalctl --unit=gpm.service », in French, yes, sorry for that too, but the interesting part is in english in fact. Here is the line with the interesting part: systemd[1]: /lib/systemd/system/gpm.service:7: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether. But for me, the issue is simple, I think. - Service section of /lib/systemd/system/gpm.service is: [Service] ExecStart=/usr/sbin/gpm -m /dev/input/mice -t exps2 StandardOutput=syslog Type=forking PIDFile=/run/gpm.pid - Service section of /lib/systemd/system/gpm.service should be: [Service] ExecStart=/usr/sbin/gpm -m /dev/input/mice -t exps2 StandardOutput=journal Type=forking PIDFile=/run/gpm.pid So, just change StandardOutput=syslog, to StandardOutput=journal, am I wrong? I will try to override it, using « sudo systemctl edit gpm.service ». And we will see what happens. For information, the steps to reproduce are in my original post: 1.Start GPM service at boot, 2.Watch journalctl when boot is done, 3.Search for gpm entries. Ok, I will put ~amd64 for sys-libs/gpm in accepted keywords, and use =sys-libs/gpm-1.20.7-r5. *** This bug has been marked as a duplicate of bug 792822 *** |