Skip to content

contrib/openrc: why put the pidfile in run/i2pd directory? #2187

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fkobi opened this issue May 6, 2025 · 2 comments
Open

contrib/openrc: why put the pidfile in run/i2pd directory? #2187

fkobi opened this issue May 6, 2025 · 2 comments

Comments

@fkobi
Copy link

fkobi commented May 6, 2025

From what I can tell the only file being put there is the pidfile.

It does not make sense to have a directory for a single file.
Is there some reason for that?

EDIT: from my testing the process does not start if pidfile is just in run/ but I would like to read an explanation still.

@r4sas
Copy link
Member

r4sas commented May 7, 2025

Our openrc scripts uses /var/run. If you use package from any package manager, tell us which system are you using.

pidfile="/var/run/i2pd/i2pd.pid"

Or better ask your package maintainer why he did that.

@fkobi fkobi changed the title contrib/openrc: why put the pidfile in /run/i2pd directory? contrib/openrc: why put the pidfile in run/i2pd directory? May 8, 2025
@fkobi
Copy link
Author

fkobi commented May 8, 2025

Our openrc scripts uses /var/run.

It has been deprecated with FHS 3.0 and I think it's worth it to change it to just /run.
This is not what I wanted to ask here -- for my question the path to run/ is irrelevant.

If you use package from any package manager, tell us which system are you using.

I use Gentoo's package but it ships with downstream openrc files, which I want to improve.


I did not want to ask about /path/to/run/i2pd/ but why do we have a run/i2pd directory if it's only purpose is to store a single (pid)file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants