change PIDFile default from /var/run/gitea.pid to /run/gitea.pid#12500
Conversation
This section covers more paths than the 3 listed in the heading.
….pid On most modern distributions, /var/run is deprecated and only kept for backwards compat according to https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s13.html, and is a symlink to `/run/` on modern distributions. Old Distros that still don't have `/run` can update the gitea default as described in from-source.en-us.md to point to the old location.
|
lable: kind/breaking do we realy have to change this default? |
Codecov Report
@@ Coverage Diff @@
## master #12500 +/- ##
==========================================
+ Coverage 43.49% 43.53% +0.03%
==========================================
Files 642 642
Lines 71003 71003
==========================================
+ Hits 30886 30910 +24
+ Misses 35108 35092 -16
+ Partials 5009 5001 -8
Continue to review full report at Codecov.
|
I'm not sure why gitea would need to still point to a long-deprecated location (and if so, for how long?) Most userspace tools have defaulted to use Gitea provides a documented way to change the default, and it would be part of the release notes, too. |
|
Kind of unrelated, but I question if we even need to have a PID file in the default configuration. Service managers like systemd can do without one and by not having one, we can eliminate a whole class of potential errors related to stale pid files. |
|
@silverwind We don't create a pid file by default - it is only if the user requests one. |
|
Is that an undocumented option? I can't find anything related to pid files in |
|
That's because it's not an app.ini option. It's a command line option: |
On most modern distributions, /var/run is deprecated and only kept for backwards compat according to
https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s13.html, and is a symlink to
/run/on modern distributions.Old Distros that still don't have
/runcan update the gitea default as described in from-source.en-us.md to point to the old location.Follow-up on #12391 (comment) and #12485.