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

Limitation: run commands block Finit execution, e.g. initctl stops responding #362

Closed
troglobit opened this issue Jul 30, 2023 · 0 comments
Assignees
Milestone

Comments

@troglobit
Copy link
Owner

In dead244 the documentation was updated:

Please note, however, that run commands block Finit, meaning you
cannot call initctl to start, stop, reload, or other such operations.
The only initctl commands possible are those that enable and disable
services and even then you should make sure to use the --force option
since otherwise initctl will try to connect to Finit.

This is the last major limitation of Finit after #356 was fixed. To fix
it Finit should be split in two, a front facing service end and another
one that handles service monitoring and runlevel transitions.

See also #137.

@troglobit troglobit modified the milestones: 5.0, 4.5 Jul 30, 2023
@troglobit troglobit self-assigned this Jul 31, 2023
troglobit added a commit that referenced this issue Sep 10, 2023
Follow-up to #362

Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
troglobit added a commit that referenced this issue Sep 13, 2023
Non-trivial systems, like Infix[1], require more than one lap around the
track to warm up.  This is a follow-up to issue #362, commit 4701ede, in
fixing an obvious oversight in the new sm_check_bootstrap() work.  While
there are still outstanding bootstrap tasks or services that have not
yet started, we must reschedule the worker.

Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant