Bug 1748322 - gssproxy.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/gssproxy.pid -> /run/gssproxy.pid; please update the unit file accordingly
Summary: gssproxy.service:9: PIDFile= references path below legacy directory /var/run/...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gssproxy
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Robbie Harwood
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-03 11:28 UTC by Harald Reindl
Modified: 2019-09-04 19:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-03 21:17:08 UTC
Type: Bug


Attachments (Terms of Use)

Description Harald Reindl 2019-09-03 11:28:43 UTC
/run exists for 8 years or so

Aug 29 02:09:54 localhost systemd[1]: /usr/lib/systemd/system/gssproxy.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/gssproxy.pid -> /run/gssproxy.pid; please update the unit file accordingly

Comment 1 Robbie Harwood 2019-09-03 21:17:08 UTC
Per FHS:

    The purposes of this directory were once served by /var/run. In general, programs may continue to use /var/run to fulfill the requirements set out for /run for the purposes of backwards compatibility. Programs which have migrated to use /run should cease their usage of /var/run, except as noted in the section on /var/run.

    -- https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.html#runRuntimeVariableData

In any case, I already made the change you're asking for in gssproxy-0.8.2-4, which was built back in July.  I don't think there's a point in backporting to the very released Fedora 30.

Comment 2 Harald Reindl 2019-09-03 21:41:13 UTC
don't explain me the FHS, you just should have read your syslogs in the F30 cycle and calling that change "backport" is laughable given that it's a bullet-proof change

honestly what are you guys doing that it's not common sense after alter systemd related nippets issue "systemctl daemon-reload" and look at your syslogs aka "journalctl"

Comment 3 Harald Reindl 2019-09-03 21:45:32 UTC
and to be clear: on Fedora your FHS quite is pure nonsense given that /var/run is a symlink to /run for many years, there is no point that /var/run exists *anywhere* in the distribution besides that symlink and i am sick and tired fix such stuff all the time on every machien because i read my damned syslogs and you stpit them full with useless stuff as result of your sloppy packaging

Comment 4 Harald Reindl 2019-09-04 10:04:51 UTC
and that's why such for you "cosmetic" bugs are a pain in the ass of responsible admins

9 lines due a regulary "dnf upgrade" and now imagine 50 packages spit that amount to the syslog and you try to look if there is something serious

[root@srv-rhsoft:~]$ cat messages  | grep gssproxy.service
Sep  4 12:00:01 srv-rhsoft systemd[1]: /usr/lib/systemd/system/gssproxy.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/gssproxy.pid → /run/gssproxy.pid; please update the unit file accordingly.
Sep  4 12:00:01 srv-rhsoft systemd[1]: /usr/lib/systemd/system/gssproxy.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/gssproxy.pid → /run/gssproxy.pid; please update the unit file accordingly.
Sep  4 12:00:01 srv-rhsoft systemd[1]: /usr/lib/systemd/system/gssproxy.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/gssproxy.pid → /run/gssproxy.pid; please update the unit file accordingly.
Sep  4 12:00:01 srv-rhsoft systemd[1]: /usr/lib/systemd/system/gssproxy.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/gssproxy.pid → /run/gssproxy.pid; please update the unit file accordingly.
Sep  4 12:00:01 srv-rhsoft systemd[1]: /usr/lib/systemd/system/gssproxy.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/gssproxy.pid → /run/gssproxy.pid; please update the unit file accordingly.
Sep  4 12:00:07 srv-rhsoft systemd[1]: /usr/lib/systemd/system/gssproxy.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/gssproxy.pid → /run/gssproxy.pid; please update the unit file accordingly.
Sep  4 12:00:07 srv-rhsoft systemd[1]: /usr/lib/systemd/system/gssproxy.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/gssproxy.pid → /run/gssproxy.pid; please update the unit file accordingly.
Sep  4 12:00:07 srv-rhsoft systemd[1]: /usr/lib/systemd/system/gssproxy.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/gssproxy.pid → /run/gssproxy.pid; please update the unit file accordingly.
Sep  4 12:00:07 srv-rhsoft systemd[1]: /usr/lib/systemd/system/gssproxy.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/gssproxy.pid → /run/gssproxy.pid; please update the unit file accordingly.


Note You need to log in before you can comment on or make changes to this bug.