Add an option to invoke a startup delay between starting each jail #844
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes it can be beneficial that multiple jails to not all start immediately one after the other. For example, I have a PostgreSQL jail which runs databases used in multiple other jails. On occasion, one of my other jails fails to successfully start services within it after reboot of the host because that service depends on postgresql which isn't accepting incoming connections, yet.
Ideally, these services would have appropriate rc scripts to cater for when a database isn't ready, but as not all of them do it can be a useful workaround to have a delay between jail startups with enough time for dependencies to start up first. This, coupled with a dependency ordered
bastille_list
can save a lot of manual intervention at reboot.Apologies if this has been covered elsewhere and I have missed it, isn't within scope of the project or if you feel there's a better way to handle this then please do as you wish.