Skip to content
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

OpenRC service script does not work #1914

Open
joshuaspiral opened this issue Feb 5, 2022 · 7 comments
Open

OpenRC service script does not work #1914

joshuaspiral opened this issue Feb 5, 2022 · 7 comments

Comments

@joshuaspiral
Copy link

Currently on alpine Linux, the OpenRC script does not work.

@progval
Copy link
Contributor

progval commented Feb 5, 2022

What is the issue?

@joshuaspiral
Copy link
Author

It does not run, when I restart/reload the service, it says * start-stop-daemon: no matching processes found [ ok ]

@progval
Copy link
Contributor

progval commented Feb 5, 2022

@thesamesam any idea what's up?

@tacerus
Copy link
Contributor

tacerus commented Feb 5, 2022

Did you install start-stop-daemon / is it actually a binary contained in PATH?

@joshuaspiral
Copy link
Author

Yes, start-stop-daemon is in /sbin and /sbin is in PATH

@thesamesam
Copy link
Contributor

I'll spin up an Alpine container later and give it a poke. Thank you for the report!

gentoo-bot pushed a commit to gentoo/gentoo that referenced this issue Feb 19, 2022
- Mostly init script fixes:
-- Add logging to init script
-- Add delay so OpenRC realises if we crashed quickly b/c of e.g. bad config
   file
-- General cleanups (like supporting multiple instances, style changes)

- Enable tests (yay! the needed files are included in tarballs now)
- Drop obsolete BDEPEND (go-module lower bound is higher)
- Drop obsolete src_compile arg to go (default in min Go in eclass)
- EAPI 8

Bug: ergochat/ergo#1914
Thanks-to: Douglas Freed <dwfreed@mtu.edu>
Thanks-to: William Hubbs <williamh@gentoo.org>
Signed-off-by: Sam James <sam@gentoo.org>
@thesamesam
Copy link
Contributor

Sorry for the delay @joshuaspiral, we've been having some renovations done and it's a bit hectic.

Could you try #1920? It should at least make it easier to see what's going wrong.

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

4 participants