diff options
| -rw-r--r-- | doc/faq.html | 20 | ||||
| -rw-r--r-- | doc/index.html | 16 | ||||
| -rw-r--r-- | doc/overview.html | 20 | ||||
| -rw-r--r-- | doc/s6-rc-bundle.html | 10 | ||||
| -rw-r--r-- | doc/s6-rc-compile.html | 28 | ||||
| -rw-r--r-- | doc/s6-rc-db.html | 6 | ||||
| -rw-r--r-- | doc/s6-rc-dryrun.html | 6 | ||||
| -rw-r--r-- | doc/s6-rc-fdholder-filler.html | 14 | ||||
| -rw-r--r-- | doc/s6-rc-init.html | 14 | ||||
| -rw-r--r-- | doc/s6-rc-oneshot-run.html | 6 | ||||
| -rw-r--r-- | doc/s6-rc-update.html | 10 | ||||
| -rw-r--r-- | doc/s6-rc.html | 12 | ||||
| -rw-r--r-- | doc/upgrade.html | 56 | ||||
| -rw-r--r-- | doc/why.html | 24 |
14 files changed, 121 insertions, 121 deletions
diff --git a/doc/faq.html b/doc/faq.html index 09c3a99..bfb995b 100644 --- a/doc/faq.html +++ b/doc/faq.html @@ -6,14 +6,14 @@ <title>s6-rc: FAQ</title> <meta name="Description" content="s6-rc: FAQ" /> <meta name="Keywords" content="s6-rc faq frequently asked questions" /> - <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> --> + <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> --> </head> <body> <p> <a href="index.html">s6-rc</a><br /> -<a href="http://skarnet.org/software/">Software</a><br /> -<a href="http://skarnet.org/">skarnet.org</a> +<a href="//skarnet.org/software/">Software</a><br /> +<a href="//skarnet.org/">skarnet.org</a> </p> <h1> s6-rc: Frequently Asked Questions </h1> @@ -93,7 +93,7 @@ file. Using the filesystem as a key-value store is a good technique to avoid parsing, and skarnet.org packages do it everywhere: for instance, -<a href="http://skarnet.org/software/s6/s6-envdir.html">s6-envdir</a> +<a href="//skarnet.org/software/s6/s6-envdir.html">s6-envdir</a> uses the file name as a key and the file contents as a value. The s6-rc-compile source format is just another instance of this technique. @@ -196,7 +196,7 @@ time you compile a service database, you could run: <li> When you compile a new service database, always compile it to a unique name, preferrably in the same directory as your current compiled database. You can for instance use a TAI64N timestamp, obtained by -<a href="http://skarnet.org/software/s6-portable-utils/s6-clock.html">s6-clock</a>, +<a href="//skarnet.org/software/s6-portable-utils/s6-clock.html">s6-clock</a>, to create such a name: <pre> stamp=`s6-clock` @@ -218,14 +218,14 @@ new database will be used on the next boot, atomically update the link: s6-ln -nsf compiled-$stamp /etc/s6-rc/compiled </pre> The use of the -<a href="http://skarnet.org/software/s6-portable-utils/s6-ln.html">s6-ln</a> +<a href="//skarnet.org/software/s6-portable-utils/s6-ln.html">s6-ln</a> utility is recommended, because the <a href="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/ln.html">ln</a> standard actually <em>forbids</em> an atomic replacement, so utilities that follow it to the letter, for instance, <tt>ln</tt> from GNU coreutils, cannot be atomic: they first remove the old link, then create the new one. If you do not have -<a href="http://skarnet.org/software/s6-portable-utils/s6-ln.html">s6-ln</a>, +<a href="//skarnet.org/software/s6-portable-utils/s6-ln.html">s6-ln</a>, you need to perform an unintuitive workaround to get POSIX-compliant tools to do the right thing: <tt>ln -sf compiled-$stamp /etc/s6-rc/compiled/compiled && @@ -284,7 +284,7 @@ using OpenRC </li> You can now run compile your s6-rc service database, and use the <a href="s6-rc.html">s6-rc</a> engine as your service manager. Transitions will use your original init scripts, and the supervision -features of <a href="http://skarnet.org/software/s6/">s6</a> will +features of <a href="//skarnet.org/software/s6/">s6</a> will not be used, but you will get proper dependency tracking and easy state changes. </p> @@ -321,7 +321,7 @@ bundle that contains nothing at all! <p> In your boot script (<tt>/etc/rc.init</tt>, for instance, if you're using -<a href="http://skarnet.org/software/s6-linux-init/">s6-linux-init</a>), +<a href="//skarnet.org/software/s6-linux-init/">s6-linux-init</a>), after invoking <a href="s6-rc-init.html">s6-rc-init</a>, just ask <a href="s6-rc.html">s6-rc</a> to start the set of services you want up @@ -416,7 +416,7 @@ addressed by <em>Unix distributions</em>. </p> <p> - Like the rest of <a href="http://skarnet.org/software/">skarnet.org + Like the rest of <a href="//skarnet.org/software/">skarnet.org software</a>, s6-rc aims to provide <em>mechanism, not policy</em>: it is OS-agnostic and distribution-agnostic. Providing boot scripts, or anything of this kind, would go against this principle; it is diff --git a/doc/index.html b/doc/index.html index e4132c5..c83d0f3 100644 --- a/doc/index.html +++ b/doc/index.html @@ -6,13 +6,13 @@ <title>s6-rc - a service manager for s6</title> <meta name="Description" content="s6-rc - a service manager for s6" /> <meta name="Keywords" content="s6 rc unix s6-rc init service management rc.d scripts administration root laurent bercot ska skarnet" /> - <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> --> + <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> --> </head> <body> <p> -<a href="http://skarnet.org/software/">Software</a><br /> -<a href="http://skarnet.org/">skarnet.org</a> +<a href="//skarnet.org/software/">Software</a><br /> +<a href="//skarnet.org/">skarnet.org</a> </p> <h1> s6-rc </h1> @@ -21,7 +21,7 @@ <p> s6-rc is a service manager for -<a href="http://skarnet.org/software/s6/">s6</a>-based +<a href="//skarnet.org/software/s6/">s6</a>-based systems, i.e. a suite of programs that can start and stop services, both long-running daemons and one-time initialization scripts, in the proper order according to a @@ -47,11 +47,11 @@ scripts are also run in a controlled environment. <ul> <li> A POSIX-compliant system with a standard C development environment </li> <li> GNU make, version 3.81 or later </li> - <li> <a href="http://skarnet.org/software/skalibs/">skalibs</a> version + <li> <a href="//skarnet.org/software/skalibs/">skalibs</a> version 2.5.1.0 or later </li> - <li> <a href="http://skarnet.org/software/execline/">execline</a> version + <li> <a href="//skarnet.org/software/execline/">execline</a> version 2.3.0.1 or later </li> - <li> <a href="http://skarnet.org/software/s6/">s6</a> version + <li> <a href="//skarnet.org/software/s6/">s6</a> version 2.5.1.0 or later </li> </ul> @@ -125,7 +125,7 @@ the previous versions of s6-rc and the current one. </li> <ul> <li> <tt>s6-rc</tt> is discussed on the -<a href="http://skarnet.org/lists.html#skaware">skaware</a> mailing-list. </li> +<a href="//skarnet.org/lists.html#skaware">skaware</a> mailing-list. </li> </ul> <h3> Similar work </h3> diff --git a/doc/overview.html b/doc/overview.html index 12d5e4d..c585cbb 100644 --- a/doc/overview.html +++ b/doc/overview.html @@ -6,14 +6,14 @@ <title>s6-rc: an overview</title> <meta name="Description" content="s6-rc: an overview" /> <meta name="Keywords" content="s6-rc overview" /> - <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> --> + <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> --> </head> <body> <p> <a href="index.html">s6-rc</a><br /> -<a href="http://skarnet.org/software/">Software</a><br /> -<a href="http://skarnet.org/">skarnet.org</a> +<a href="//skarnet.org/software/">Software</a><br /> +<a href="//skarnet.org/">skarnet.org</a> </p> <h1> An overview of s6-rc </h1> @@ -59,11 +59,11 @@ around while the filesystem is mounted. <ul> <li> A <em>longrun</em> is the exact equivalent of a <em>service</em> in the supervision sense. It is defined by a -<a href="http://skarnet.org/software/s6/servicedir.html">service +<a href="//skarnet.org/software/s6/servicedir.html">service directory</a>, with a run script and optional other data. The service is considered <em>up</em> as long as the long-lived process is alive and, for daemons that support it, has -<a href="http://skarnet.org/software/s6/notifywhenup.html">notified +<a href="//skarnet.org/software/s6/notifywhenup.html">notified its readiness</a>. It is considered <em>down</em> otherwise. </li> <li> A <em>oneshot</em>, on the other hand, is totally unknown from supervision suites, because there is no daemon to manage. @@ -143,15 +143,15 @@ them in a human-friendly format. </li> <ul> <li> First, the chosen init should make sure that a -<a href="http://skarnet.org/software/s6/">s6</a> +<a href="//skarnet.org/software/s6/">s6</a> supervision tree is up and running. s6-rc will only work if there is an active -<a href="http://skarnet.org/software/s6/s6-svscan.html">s6-svscan</a> +<a href="//skarnet.org/software/s6/s6-svscan.html">s6-svscan</a> process monitoring a -<a href="http://skarnet.org/software/s6/scandir.html">scan +<a href="//skarnet.org/software/s6/scandir.html">scan directory</a>. On Linux, for instance, it is possible to achieve such a state by using an init created by the -<a href="http://skarnet.org/software/s6-linux-init/s6-linux-init-maker.html">s6-linux-init-maker</a> +<a href="//skarnet.org/software/s6-linux-init/s6-linux-init-maker.html">s6-linux-init-maker</a> tool: when control reaches stage 2, s6-svscan is guaranteed to run, so using s6-rc in the stage 2 script is the way to go. </li> <li> The boot process, let's name it <em>stage2</em>, should then call the @@ -194,7 +194,7 @@ managed by s6-rc should be brought down in the proper order (via the <tt>s6-rc -da change</tt> command). Once all those services have been brought down successfully, the final shutdown procedure can take place; for instance, if s6-svscan is running as process 1 with the -<a href="http://skarnet.org/software/s6-linux-init/">s6-linux-init</a> +<a href="//skarnet.org/software/s6-linux-init/">s6-linux-init</a> defaults, <tt>s6-svscanctl -6 /run/service</tt> will kill the supervision tree and call <tt>/etc/rc.shutdown reboot</tt>, which should reboot the machine. diff --git a/doc/s6-rc-bundle.html b/doc/s6-rc-bundle.html index 21a1f8a..6365f32 100644 --- a/doc/s6-rc-bundle.html +++ b/doc/s6-rc-bundle.html @@ -6,14 +6,14 @@ <title>s6-rc: the s6-rc-bundle program</title> <meta name="Description" content="s6-rc: the s6-rc-bundle program" /> <meta name="Keywords" content="s6-rc offline database dump command rc init dependency state management services" /> - <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> --> + <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> --> </head> <body> <p> <a href="index.html">s6-rc</a><br /> -<a href="http://skarnet.org/software/">Software</a><br /> -<a href="http://skarnet.org/">skarnet.org</a> +<a href="//skarnet.org/software/">Software</a><br /> +<a href="//skarnet.org/">skarnet.org</a> </p> <h1> The s6-rc-bundle program </h1> @@ -112,9 +112,9 @@ s6-rc-bundle invocation. <p> Performs multiple bundle deletions and additions. This subcommand is best -used in an <a href="http://skarnet.org/software/execline/">execline</a> +used in an <a href="//skarnet.org/software/execline/">execline</a> script, because it uses -<a href="http://skarnet.org/software/execline/el_semicolon.html">blocks</a>. +<a href="//skarnet.org/software/execline/el_semicolon.html">blocks</a>. </p> <p> diff --git a/doc/s6-rc-compile.html b/doc/s6-rc-compile.html index 453c6ac..d78e7ad 100644 --- a/doc/s6-rc-compile.html +++ b/doc/s6-rc-compile.html @@ -6,14 +6,14 @@ <title>s6-rc: the s6-rc-compile program</title> <meta name="Description" content="s6-rc: the s6-rc-compile program" /> <meta name="Keywords" content="s6-rc offline database compilation command rc init dependency state management services" /> - <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> --> + <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> --> </head> <body> <p> <a href="index.html">s6-rc</a><br /> -<a href="http://skarnet.org/software/">Software</a><br /> -<a href="http://skarnet.org/">skarnet.org</a> +<a href="//skarnet.org/software/">Software</a><br /> +<a href="//skarnet.org/">skarnet.org</a> </p> <h1> The s6-rc-compile program </h1> @@ -73,7 +73,7 @@ use this database with <a href="s6-rc.html">s6-rc</a> to start and stop services. <em>gids</em> must be a comma-separated list of numerical GIDs. </li> <li> <tt>-h <em>fdhuser</em></tt> : arrange for the -<a href="http://skarnet.org/software/s6/s6-fdholder-daemon.html">s6-fdholder-daemon</a> +<a href="//skarnet.org/software/s6/s6-fdholder-daemon.html">s6-fdholder-daemon</a> program, which maintains the pipes for the longrun pipelines, to run as user <em>fdhuser</em>. By default, it runs as the user owning the supervision tree, i.e. most likely <tt>root</tt>. </li> @@ -201,7 +201,7 @@ complain and exit 1. <ul> <li> Two regular files named <tt>up</tt> and <tt>down</tt>, which must each contain a single Unix command line. The files will be interpreted by the -<a href="http://skarnet.org/software/execline/execlineb.html">execlineb</a> +<a href="//skarnet.org/software/execline/execlineb.html">execlineb</a> lexer at compile time and the results will be stored into the compiled database in an internal form. <tt>up</tt> will be run when the service is started, and <tt>down</tt> will be executed when the service @@ -215,10 +215,10 @@ does nothing and always succeeds. </li> <p> <tt>up</tt> and <tt>down</tt> are interpreted by -<a href="http://skarnet.org/software/execline/execlineb.html">execlineb</a>, but +<a href="//skarnet.org/software/execline/execlineb.html">execlineb</a>, but that does not mean they have to be entirely written in the -<a href="http://skarnet.org/software/execline/">execline</a> language. The -<a href="http://skarnet.org/software/execline/execlineb.html">execlineb</a> +<a href="//skarnet.org/software/execline/">execline</a> language. The +<a href="//skarnet.org/software/execline/execlineb.html">execlineb</a> lexer is only used because it can compile a Unix command line from a text file and store the compiled result, whereas a shell would have to be invoked everytime the script is run. There are many ways to write <tt>up</tt> and @@ -248,7 +248,7 @@ You don't. <p> The s6-rc service definition directory for a longrun service is similar to -a <a href="http://skarnet.org/software/s6/servicedir.html">s6 service +a <a href="//skarnet.org/software/s6/servicedir.html">s6 service directory</a>, but there are a few differences: </p> @@ -277,9 +277,9 @@ about pipelines. </li> named <tt>finish</tt>, <tt>notification-fd</tt>, <tt>timeout-kill</tt>, <tt>timeout-finish</tt> and <tt>nosetsid</tt>. These files will be copied, or recreated, in the generated -<a href="http://skarnet.org/software/s6/servicedir.html">service directory</a>: +<a href="//skarnet.org/software/s6/servicedir.html">service directory</a>: they are meant to be used by the -<a href="http://skarnet.org/software/s6/s6-supervise.html">s6-supervise</a> +<a href="//skarnet.org/software/s6/s6-supervise.html">s6-supervise</a> process that will manage the longrun service. </li> <li> Optional directories named <tt>data</tt> and <tt>env</tt>. These will be copied verbatim into the generated service directory. </li> @@ -311,7 +311,7 @@ use relative paths, not absolute ones. <p> Note that you cannot create a <tt>./down</tt> file for -<a href="http://skarnet.org/software/s6/s6-supervise.html">s6-supervise</a> +<a href="//skarnet.org/software/s6/s6-supervise.html">s6-supervise</a> in a generated service directory. Even if such a file exists in the definition directory, it will be ignored - it will not be replicated in the service directory. @@ -369,7 +369,7 @@ detect and reject cycles as well as collisions. <p> The pipe linking a producer with a consumer is created and stored at run-time in a -<a href="http://skarnet.org/software/s6/s6-fdholder-daemon.html">s6-fdholder-daemon</a> +<a href="//skarnet.org/software/s6/s6-fdholder-daemon.html">s6-fdholder-daemon</a> instance managed by an automatically generated longrun service named <tt>s6rc-fdholder</tt>. </p> @@ -381,7 +381,7 @@ instance managed by an automatically generated longrun service named of service definition directories, which is actually a working, valid set for a Linux system running <a href="http://busybox.net/">busybox</a> and the -<a href="http://skarnet.org/software/">skarnet.org</a> packages; of course, only +<a href="//skarnet.org/software/">skarnet.org</a> packages; of course, only the service definition set has been kept, and private information has been removed, so it won't work out-of-the-box without the proper specific files, notably configuration in <tt>/etc</tt> - but nevertheless, you can browse the diff --git a/doc/s6-rc-db.html b/doc/s6-rc-db.html index 5c664f5..bc527a6 100644 --- a/doc/s6-rc-db.html +++ b/doc/s6-rc-db.html @@ -6,14 +6,14 @@ <title>s6-rc: the s6-rc-db program</title> <meta name="Description" content="s6-rc: the s6-rc-db program" /> <meta name="Keywords" content="s6-rc offline database dump command rc init dependency state management services" /> - <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> --> + <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> --> </head> <body> <p> <a href="index.html">s6-rc</a><br /> -<a href="http://skarnet.org/software/">Software</a><br /> -<a href="http://skarnet.org/">skarnet.org</a> +<a href="//skarnet.org/software/">Software</a><br /> +<a href="//skarnet.org/">skarnet.org</a> </p> <h1> The s6-rc-db program </h1> diff --git a/doc/s6-rc-dryrun.html b/doc/s6-rc-dryrun.html index ee23d3b..11210bd 100644 --- a/doc/s6-rc-dryrun.html +++ b/doc/s6-rc-dryrun.html @@ -6,14 +6,14 @@ <title>s6-rc: the s6-rc-dryrun program</title> <meta name="Description" content="s6-rc: the s6-rc-dryrun program" /> <meta name="Keywords" content="s6-rc dry run s6-rc-dryrun command rc init dependency state management services" /> - <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> --> + <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> --> </head> <body> <p> <a href="index.html">s6-rc</a><br /> -<a href="http://skarnet.org/software/">Software</a><br /> -<a href="http://skarnet.org/">skarnet.org</a> +<a href="//skarnet.org/software/">Software</a><br /> +<a href="//skarnet.org/">skarnet.org</a> </p> <h1> The s6-rc-dryrun internal program </h1> diff --git a/doc/s6-rc-fdholder-filler.html b/doc/s6-rc-fdholder-filler.html index a835663..4904afd 100644 --- a/doc/s6-rc-fdholder-filler.html +++ b/doc/s6-rc-fdholder-filler.html @@ -6,21 +6,21 @@ <title>s6-rc: the s6-rc-fdholder-filler program</title> <meta name="Description" content="s6-rc: the s6-rc-fdholder-filler program" /> <meta name="Keywords" content="s6-rc dry run s6-rc-fdholder-filler internal s6-rc fdholder s6rc-fdholder pipe" /> - <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> --> + <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> --> </head> <body> <p> <a href="index.html">s6-rc</a><br /> -<a href="http://skarnet.org/software/">Software</a><br /> -<a href="http://skarnet.org/">skarnet.org</a> +<a href="//skarnet.org/software/">Software</a><br /> +<a href="//skarnet.org/">skarnet.org</a> </p> <h1> The s6-rc-fdholder-filler internal program </h1> <p> s6-rc-fdholder-filler creates anonymous pipes and stores them into a -<a href="http://skarnet.org/software/s6/s6-fdholderd.html">s6-fdholderd</a> +<a href="//skarnet.org/software/s6/s6-fdholderd.html">s6-fdholderd</a> "fd-holding" daemon. </p> @@ -40,14 +40,14 @@ in internal scripts created by <ul> <li> s6-rc-fdholder-filler expects file descriptor 6 to be open and connected to the -<a href="http://skarnet.org/software/s6/s6-fdholderd.html">s6-fdholderd</a> +<a href="//skarnet.org/software/s6/s6-fdholderd.html">s6-fdholderd</a> daemon instance managed by s6-rc as the internal <em>s6rc-fdholder</em> service. </li> <li> It reads a list of longrun names from its stdin, one per line. Empty lines are ignored; comments starting with <tt>#</tt> are ignored; leading whitespace is ignored, but trailing whitespace is not. </li> <li> For every name <em>longrun</em> that it finds, it creates an anonymous pipe, and stores both ends of that pipe into the -<a href="http://skarnet.org/software/s6/s6-fdholderd.html">s6-fdholderd</a> +<a href="//skarnet.org/software/s6/s6-fdholderd.html">s6-fdholderd</a> instance, with the <tt>pipe:s6-rc-r-<em>longrun</em></tt> (for the reading end) and <tt>pipe:s6-rc-w-<em>longrun</em></tt> (for the writing end) identifiers, and an infinite timeout. </li> @@ -79,7 +79,7 @@ default, <em>timeout</em> is 0, meaning infinite. </li> should only be used to understand s6-rc internals. </li> <li> s6-rc-fdholder-filler is used in the <tt>s6rc-fdholder</tt> internal service's run script, right after the -<a href="http://skarnet.org/software/s6/s6-fdholderd.html">s6-fdholderd</a> +<a href="//skarnet.org/software/s6/s6-fdholderd.html">s6-fdholderd</a> daemon is started; its arguments are the names of all the consumer longrun services declared in the service database. </li> <li> The point is to create all the pipes for the longrun pipelines in diff --git a/doc/s6-rc-init.html b/doc/s6-rc-init.html index c0ae6fc..54692bf 100644 --- a/doc/s6-rc-init.html +++ b/doc/s6-rc-init.html @@ -6,14 +6,14 @@ <title>s6-rc: the s6-rc-init program</title> <meta name="Description" content="s6-rc: the s6-rc-init program" /> <meta name="Keywords" content="s6-rc command s6-rc-init rc init dependency state management services" /> - <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> --> + <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> --> </head> <body> <p> <a href="index.html">s6-rc</a><br /> -<a href="http://skarnet.org/software/">Software</a><br /> -<a href="http://skarnet.org/">skarnet.org</a> +<a href="//skarnet.org/software/">Software</a><br /> +<a href="//skarnet.org/">skarnet.org</a> </p> <h1> The s6-rc-init program </h1> @@ -37,7 +37,7 @@ invocation of the <li> s6-rc-init expects to find a <em>compiled service database</em> in <em>compiled</em>. It expects to be able to create a directory named <em>live</em>. It also expects that an instance of -<a href="http://skarnet.org/software/s6/s6-svscan.html">s6-svscan</a> +<a href="//skarnet.org/software/s6/s6-svscan.html">s6-svscan</a> is running on <em>scandir</em>. </li> <li> s6-rc-init initializes the live state in <em>live</em>. It declares <em>compiled</em> as the current service database and @@ -46,9 +46,9 @@ sets the state as "all services down". </li> the service directories declared by <em>compiled</em> into a subdirectory of <em>live</em>, adds <tt>./down</tt> files to the live copies and links those live copies into <em>scandir</em>. It then triggers -<a href="http://skarnet.org/software/s6/s6-svscan.html">s6-svscan</a>, +<a href="//skarnet.org/software/s6/s6-svscan.html">s6-svscan</a>, which will pick up the new service directories and start -<a href="http://skarnet.org/software/s6/s6-supervise.html">s6-supervise</a> +<a href="//skarnet.org/software/s6/s6-supervise.html">s6-supervise</a> processes on them - but the service themselves will not be started right away, because of the <tt>./down</tt> files. </li> <li> s6-rc-init waits for all s6-supervise processes to be @@ -104,7 +104,7 @@ invocation of the <a href="s6-rc.html">s6-rc change</a> command.) <p> For instance, when using an init created by -<a href="http://skarnet.org/software/s6-linux-init/">s6-linux-init</a>, +<a href="//skarnet.org/software/s6-linux-init/">s6-linux-init</a>, <tt>s6-rc-init</tt> should be the first command in the <em>stage2</em> (by default <tt>/etc/rc.init</tt>) script. </p> diff --git a/doc/s6-rc-oneshot-run.html b/doc/s6-rc-oneshot-run.html index 8cddcb5..49ed63b 100644 --- a/doc/s6-rc-oneshot-run.html +++ b/doc/s6-rc-oneshot-run.html @@ -6,14 +6,14 @@ <title>s6-rc: the s6-rc-oneshot-run program</title> <meta name="Description" content="s6-rc: the s6-rc-oneshot-run program" /> <meta name="Keywords" content="s6-rc dry run s6-rc-oneshot-run command oneshot runner service manager" /> - <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> --> + <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> --> </head> <body> <p> <a href="index.html">s6-rc</a><br /> -<a href="http://skarnet.org/software/">Software</a><br /> -<a href="http://skarnet.org/">skarnet.org</a> +<a href="//skarnet.org/software/">Software</a><br /> +<a href="//skarnet.org/">skarnet.org</a> </p> <h1> The s6-rc-oneshot-run internal program </h1> diff --git a/doc/s6-rc-update.html b/doc/s6-rc-update.html index 52ab42d..165f8de 100644 --- a/doc/s6-rc-update.html +++ b/doc/s6-rc-update.html @@ -6,14 +6,14 @@ <title>s6-rc: the s6-rc-update program</title> <meta name="Description" content="s6-rc: the s6-rc-update program" /> <meta name="Keywords" content="s6-rc command rc update s6-rc-update init dependency state management services" /> - <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> --> + <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> --> </head> <body> <p> <a href="index.html">s6-rc</a><br /> -<a href="http://skarnet.org/software/">Software</a><br /> -<a href="http://skarnet.org/">skarnet.org</a> +<a href="//skarnet.org/software/">Software</a><br /> +<a href="//skarnet.org/">skarnet.org</a> </p> <h1> The s6-rc-update program </h1> @@ -194,7 +194,7 @@ the next. <p> A line is lexed into words by the -<a href="http://skarnet.org/software/execline/execlineb.html">execlineb</a> +<a href="//skarnet.org/software/execline/execlineb.html">execlineb</a> lexer, which means that words are normally separated by whitespace, but can be quoted, that <tt>#</tt> comments are recognized, etc. </p> @@ -256,7 +256,7 @@ to the real directory containing the live information, not the name of the real directory. </li> <li> If a longrun service is renamed from <em>oldname</em> to <em>newname</em>, but not restarted, the -<a href="http://skarnet.org/software/s6/s6-supervise.html">s6-supervise</a> +<a href="//skarnet.org/software/s6/s6-supervise.html">s6-supervise</a> process in charge of it will still show up in the process list as <tt>s6-supervise <em>oldname</em></tt>. This is purely cosmetic and will have no impact on the service; nevertheless, if you wish to avoid that, diff --git a/doc/s6-rc.html b/doc/s6-rc.html index a6e64d9..957c108 100644 --- a/doc/s6-rc.html +++ b/doc/s6-rc.html @@ -6,14 +6,14 @@ <title>s6-rc: the s6-rc program</title> <meta name="Description" content="s6-rc: the s6-rc program" /> <meta name="Keywords" content="s6-rc command rc init dependency state management services" /> - <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> --> + <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> --> </head> <body> <p> <a href="index.html">s6-rc</a><br /> -<a href="http://skarnet.org/software/">Software</a><br /> -<a href="http://skarnet.org/">skarnet.org</a> +<a href="//skarnet.org/software/">Software</a><br /> +<a href="//skarnet.org/">skarnet.org</a> </p> <h1> The s6-rc program </h1> @@ -234,14 +234,14 @@ is considered down by s6-rc will have a <tt>./down</tt> file in its live service directory; a service that is considered up by s6-rc will not.) The transition is considered successful as soon as the daemon dies (for down transitions), or becomes up and -<a href="http://skarnet.org/software/s6/notifywhenup.html">ready</a> +<a href="//skarnet.org/software/s6/notifywhenup.html">ready</a> (for up transitions). If a longrun service does not support readiness notification, the -<a href="http://skarnet.org/software/s6/s6-svc.html">s6-svc</a> +<a href="//skarnet.org/software/s6/s6-svc.html">s6-svc</a> command that is invoked by s6-rc will print a warning message, and the transition will be considered successful as soon as the daemon is up, i.e. as soon as the <tt>./run</tt> script is executed by -<a href="http://skarnet.org/software/s6/s6-supervise.html">s6-supervise</a>. +<a href="//skarnet.org/software/s6/s6-supervise.html">s6-supervise</a>. </p> <p> diff --git a/doc/upgrade.html b/doc/upgrade.html index a35db65..3db2fd0 100644 --- a/doc/upgrade.html +++ b/doc/upgrade.html @@ -6,14 +6,14 @@ <title>s6-rc: how to upgrade</title> <meta name="Description" content="s6-rc: how to upgrade" /> <meta name="Keywords" content="s6-rc installation upgrade" /> - <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> --> + <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> --> </head> <body> <p> <a href="index.html">s6-rc</a><br /> -<a href="http://skarnet.org/software/">Software</a><br /> -<a href="http://skarnet.org/">skarnet.org</a> +<a href="//skarnet.org/software/">Software</a><br /> +<a href="//skarnet.org/">skarnet.org</a> </p> <h1> What has changed in s6-rc </h1> @@ -21,22 +21,22 @@ <h2> in 0.2.0.1 </h2> <ul> - <li> <a href="http://skarnet.org/software/skalibs/">skalibs</a> + <li> <a href="//skarnet.org/software/skalibs/">skalibs</a> dependency bumped to 2.5.1.0. </li> - <li> <a href="http://skarnet.org/software/execline/">execline</a> + <li> <a href="//skarnet.org/software/execline/">execline</a> dependency bumped to 2.3.0.1. </li> - <li> <a href="http://skarnet.org/software/s6/">s6</a> + <li> <a href="//skarnet.org/software/s6/">s6</a> dependency bumped to 2.5.1.0. </li> </ul> <h2> in 0.2.0.0 </h2> <ul> - <li> <a href="http://skarnet.org/software/skalibs/">skalibs</a> + <li> <a href="//skarnet.org/software/skalibs/">skalibs</a> dependency bumped to 2.5.0.0. </li> - <li> <a href="http://skarnet.org/software/execline/">execline</a> + <li> <a href="//skarnet.org/software/execline/">execline</a> dependency bumped to 2.3.0.0. </li> - <li> <a href="http://skarnet.org/software/s6/">s6</a> + <li> <a href="//skarnet.org/software/s6/">s6</a> dependency bumped to 2.5.0.0. </li> <li> s6-rc commands taking a lock on the live directory or the service database now fail instantly if the lock is already held. @@ -47,29 +47,29 @@ lock is released" behaviour. </li> <h2> in 0.1.0.0 </h2> <ul> - <li> <a href="http://skarnet.org/software/skalibs/">skalibs</a> + <li> <a href="//skarnet.org/software/skalibs/">skalibs</a> dependency bumped to 2.4.0.0. </li> - <li> <a href="http://skarnet.org/software/execline/">execline</a> + <li> <a href="//skarnet.org/software/execline/">execline</a> dependency bumped to 2.2.0.0. </li> - <li> <a href="http://skarnet.org/software/s6/">s6</a> + <li> <a href="//skarnet.org/software/s6/">s6</a> dependency bumped to 2.4.0.0. </li> </ul> <h2> in 0.0.3.0 </h2> <ul> - <li> <a href="http://skarnet.org/software/skalibs/">skalibs</a> + <li> <a href="//skarnet.org/software/skalibs/">skalibs</a> dependency bumped to 2.3.10.0. </li> - <li> <a href="http://skarnet.org/software/execline/">execline</a> + <li> <a href="//skarnet.org/software/execline/">execline</a> dependency bumped to 2.1.5.0. </li> - <li> <a href="http://skarnet.org/software/s6/">s6</a> + <li> <a href="//skarnet.org/software/s6/">s6</a> dependency bumped to 2.3.0.0. </li> </ul> <h2> in 0.0.2.1 </h2> <ul> - <li> <a href="http://skarnet.org/software/s6/">s6</a> + <li> <a href="//skarnet.org/software/s6/">s6</a> dependency bumped to 2.2.4.2. </li> </ul> @@ -78,22 +78,22 @@ dependency bumped to 2.2.4.2. </li> <ul> <li> Better exit codes for <a href="s6-rc-update.html">s6-rc-update</a>. </li> - <li> <a href="http://skarnet.org/software/skalibs/">skalibs</a> + <li> <a href="//skarnet.org/software/skalibs/">skalibs</a> dependency bumped to 2.3.8.3. </li> - <li> <a href="http://skarnet.org/software/execline/">execline</a> + <li> <a href="//skarnet.org/software/execline/">execline</a> dependency bumped to 2.1.4.5. </li> - <li> <a href="http://skarnet.org/software/s6/">s6</a> + <li> <a href="//skarnet.org/software/s6/">s6</a> dependency bumped to 2.2.4.0. </li> </ul> <h2> in 0.0.1.5 </h2> <ul> - <li> <a href="http://skarnet.org/software/skalibs/">skalibs</a> + <li> <a href="//skarnet.org/software/skalibs/">skalibs</a> dependency bumped to 2.3.8.2. </li> - <li> <a href="http://skarnet.org/software/execline/">execline</a> + <li> <a href="//skarnet.org/software/execline/">execline</a> dependency bumped to 2.1.4.4. </li> - <li> <a href="http://skarnet.org/software/s6/">s6</a> + <li> <a href="//skarnet.org/software/s6/">s6</a> dependency bumped to 2.2.3.1. </li> </ul> @@ -114,22 +114,22 @@ dependency bumped to 2.2.3.1. </li> <ul> <li> <a href="https://www.gnu.org/software/make/">GNU make</a> dependency pushed back to 3.81. </li> - <li> <a href="http://skarnet.org/software/skalibs/">skalibs</a> + <li> <a href="//skarnet.org/software/skalibs/">skalibs</a> dependency bumped to 2.3.8.0. </li> - <li> <a href="http://skarnet.org/software/execline/">execline</a> + <li> <a href="//skarnet.org/software/execline/">execline</a> dependency bumped to 2.1.4.2. </li> - <li> <a href="http://skarnet.org/software/s6/">s6</a> + <li> <a href="//skarnet.org/software/s6/">s6</a> dependency bumped to 2.2.2.0. </li> </ul> <h2> in 0.0.1.1 </h2> <ul> - <li> <a href="http://skarnet.org/software/skalibs/">skalibs</a> + <li> <a href="//skarnet.org/software/skalibs/">skalibs</a> dependency bumped to 2.3.7.1. </li> - <li> <a href="http://skarnet.org/software/execline/">execline</a> + <li> <a href="//skarnet.org/software/execline/">execline</a> dependency bumped to 2.1.4.1. </li> - <li> <a href="http://skarnet.org/software/s6/">s6</a> + <li> <a href="//skarnet.org/software/s6/">s6</a> dependency bumped to 2.2.1.1. </li> </ul> diff --git a/doc/why.html b/doc/why.html index 775f81d..157a27e 100644 --- a/doc/why.html +++ b/doc/why.html @@ -6,14 +6,14 @@ <title>s6-rc: why?</title> <meta name="Description" content="s6-rc: why?" /> <meta name="Keywords" content="s6-rc why reason rationale" /> - <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> --> + <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> --> </head> <body> <p> <a href="index.html">s6-rc</a><br /> -<a href="http://skarnet.org/software/">Software</a><br /> -<a href="http://skarnet.org/">skarnet.org</a> +<a href="//skarnet.org/software/">Software</a><br /> +<a href="//skarnet.org/">skarnet.org</a> </p> <h1> Why s6-rc ? </h1> @@ -22,7 +22,7 @@ <p> Supervision suites such as -<a href="http://skarnet.org/software/s6/">s6</a>, +<a href="//skarnet.org/software/s6/">s6</a>, <a href="http://smarden.org/runit/">runit</a>, <a href="http://b0llix.net/perp/">perp</a> or <a href="http://cr.yp.to/daemontools.html">daemontools</a> @@ -32,7 +32,7 @@ way in a controlled environment and keep it alive if it dies; they also provide daemon management tools to, among others, send signals to the daemon without knowing its PID. They can control individual long-lived processes perfectly well, and -<a href="http://skarnet.org/software/s6/">s6</a> also provides +<a href="//skarnet.org/software/s6/">s6</a> also provides tools to manage a whole supervision tree. To any system administrator concerned about reliability, supervision suites are a good thing. </p> @@ -132,7 +132,7 @@ oneshots or longruns, one by one, even when the dependency graph says that some services could be started in parallel. Also, the daemons they start are always unsupervised, even when the underlying init system provides supervision features. There usually is no -<a href="http://skarnet.org/software/s6/notifywhenup.html">readiness +<a href="//skarnet.org/software/s6/notifywhenup.html">readiness notification</a> support on daemons either, daemons are fire-and-forget (but that's more on the scripts themselves than on the frameworks). Another common criticism @@ -195,7 +195,7 @@ guys. </li> <li> <a href="http://www.freedesktop.org/wiki/Software/systemd/">systemd</a>, the main protagonist (or antagonist) in the "init wars". It has the same problems as launchd, up by an order of magnitude; -<a href="http://skarnet.org/software/s6/systemd.html">here is why</a>. +<a href="//skarnet.org/software/s6/systemd.html">here is why</a>. systemd avowedly aims to replace the whole low-level user-space of Linux systems, but its design is horrendous. It doesn't even <a href="http://ewontfix.com/15/">get readiness notification right</a>. </li> @@ -246,16 +246,16 @@ readiness notification support, reproducible script execution, and <tt>sysv-rc</tt> or OpenRC. It is <em>not</em> an init system. <strong>You can run s6-rc with any init system of your choosing.</strong> Of course, s6-rc requires a -<a href="http://skarnet.org/software/s6/">s6</a> supervision tree to be running on +<a href="//skarnet.org/software/s6/">s6</a> supervision tree to be running on the system, since it delegates the management of longrun services to that supervision tree, but it does not require that s6 be the init system itself. s6-rc will work -<a href="http://skarnet.org/software/s6/s6-svscan-1.html">when s6-svscan +<a href="//skarnet.org/software/s6/s6-svscan-1.html">when s6-svscan runs as process 1</a> (on Linux, such a setup can be easily achieved via the help of the -<a href="http://skarnet.org/software/s6-linux-init/">s6-linux-init</a> +<a href="//skarnet.org/software/s6-linux-init/">s6-linux-init</a> package), and it will also work -<a href="http://skarnet.org/software/s6/s6-svscan-not-1.html">when +<a href="//skarnet.org/software/s6/s6-svscan-not-1.html">when s6-svscan runs under another init process</a>. </li> <li> The service manager runs <em>on top of</em> a supervision suite. It does not try to make it perform boot/shutdown operations or @@ -277,7 +277,7 @@ simple, in order to allow external tools to automatically write service definitions for s6-rc - for instance for conversions between service manager formats. </li> <li> Like every -<a href="http://skarnet.org/software/">skarnet.org tool</a>, s6-rc +<a href="//skarnet.org/software/">skarnet.org tool</a>, s6-rc is made of very little code, that does its job and nothing else. The binaries are small, it is very light in memory usage, and the code paths are extremely short. </li> |