From 87b8fcabeecf2a9cff2ca596da54d6c1cf17d89f Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Sun, 14 Jun 2026 04:37:32 +0000 Subject: Prepare for 0.7.0.0; lots of changes! - s6-rc-bundle deleted. Changing bundles without recompiling is not supported anymore. (It works, but it incentivizes poor workflows; it is better to handle stuff at the source level and recompile when in doubt, that's what s6-frontend does.) - new db format, need to recompile and use s6-rc-format-upgrade on new live db - support for the reload-signal file in service directories - new reload scripts for oneshots (which is why the db format has changed) - new "s6-rc reload" command, calling s6-svc -l on longruns (which makes use of reload-signal, HUP by default) and the reload script on oneshots - the live state now tracks when a service has been explicitly brought up as opposed to by pulled by dependencies. Nothing uses the feature for now but now the tech is there for an auto-stop-if-unneeded feature. --- doc/s6-rc.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'doc/s6-rc.html') diff --git a/doc/s6-rc.html b/doc/s6-rc.html index bb16113..afd6795 100644 --- a/doc/s6-rc.html +++ b/doc/s6-rc.html @@ -252,8 +252,7 @@ given on the command line, which must all be up. For a longrun, s6-rc reload sends an s6-svc -l command to the service, which causes it to receive a SIGHUP, or any overriding signal configured in the reload-signal file. -For a oneshot, the service's up script is executed, with -an additional RC_RELOAD environment variable containing 1. +For a oneshot, the service's reload script is executed.

-- cgit v1.3.1