-
Notifications
You must be signed in to change notification settings - Fork 62
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
no place for packages to drop oneshot boot/shutdown tasks #23
Comments
Does runit even allow executing a script at shutdown? |
Yea that is what stage 3 is haha. Regarding where to invoke from, why nest inside rc.local and rc.shutdown, respectively? |
According to void-linux/void-packages#12974, there is interest in having the boot and shutdown tasks/scripts to be coupled into a directory like the run/finish files are for services. So my local/shutdown idea needs work. There is also interest in being able to enable and disable the tasks. The directories Furthermore, void-linux/void-packages#4053 demonstrates there is interest in being able to manually run the tasks during system operation. My proposal:
A command (e.g.
In stage two, the command will be invoked as And after typing all this I question if I should just learn s6-rc. Edit: remove |
The problem is all this basically can be implemented with runit with I am not interested in complicated and unique solutions to small problems like the above. |
No The proposed system is too complex, this looks like a reinvented rc system. Something like |
Could do something stupid simple, three directories |
@Duncaen how do you propose handling enable/disable? the apparmor core-service is an example of how it should not be done, from my perspective. And what about manual restarting that leah brought up? |
I agree with duncaen that it looks like you've just designed an init system, and we already have one of those. I think the problem of manually running one-shot tasks is perhaps beyond the scope of the current problems, as its looking for tooling to basically call shell scripts. We have those already; they're called shells. The goal here, as far as I'm aware, is to provide a machine hook in point for packages to add tasks they need early in startup or shutdown. They don't necessarily need to do it automatically, it could happen with a symlink like we do with runit, but it shouldn't be any more complicated than that. |
Is this solved by the combination of There are already several packages ( |
I think so. |
We honor rc.local and rc.shutdown, but these scripts are not accessible for packages to hook into. I propose adding rc.local.d and a corresponding shutdown directory to accommodate these use cases. Comments?
The text was updated successfully, but these errors were encountered: