Deprecated path /var/run being used for PIDfile in systemd unit and other places

[sanvila]

My videobridge instances show warning messages like this in the logs:

systemd[1]: /lib/systemd/system/jitsi-videobridge2.service:13: PIDFile=
references path below legacy directory /var/run/, updating /var/run/jitsi-videobridge/jitsi-videobridge.pid →
/run/jitsi-videobridge/jitsi-videobridge.pid; please update the unit file accordingly.

I believe a fix would involve locating all occurrences of var/run in the code:

rgrep var/run

and just replacing them by /run. I would do this myself because it's trivial to do, but unfortunately I don't have the resources to test it extensively. I believe that upgrades should be seamless in either case because /var/run is a symlink to /run anyway.

Thanks.

Note: The warnings have been appearing at least since Debian 10.

[damencho]

/var/run is a symlink to /run anyway

For which Debian and Ubuntu versions is this?

[sanvila]

Good question. The symlink was already there in Debian 9, released in June 2017. For Ubuntu, I believe it was already there in Ubuntu 18.04 (just checked right now using a virtual machine from Hetzner, they don't have older images to check).

[damencho]

Thanks for checking, I wonder how would the upgrade go when changing it, but this I can test.
18.04 is good enough, its the oldest we support in the moment with small adjustments before installing :)