On Wed, Jan 19, 2005 at 01:30:55AM +0100, Javier Fernández-Sanguino Peña wrote:
> --- policy.sgml.orig 2005-01-19 01:10:37.000000000 +0100
> +++ policy.sgml 2005-01-19 01:13:05.000000000 +0100
> @@ -5392,13 +5392,17 @@
> <tag><tt>force-reload</tt></tag>
> <item>cause the configuration to be reloaded if the
> service supports this, otherwise restart the
> - service.</item>
> + service,</item>
> +
> + <tag><tt>status</tt></tag>
> + <item><p>show the status of the service (either running
> + or dead).</item>
> </taglist>
I don't think this is a sufficient specification. We should make it
clear what status should display in the different case:
1) init script does not start a daemon
2.a) init script start a daemon which is running
2.b) init script start a daemon which is not running
3) init script start several daemons
4) init script was disabled in config
On Wed, Jan 19, 2005 at 01:30:55AM +0100, Javier Fernández-Sanguino Peña wrote: force-reload< /tt></tag> status< /tt></tag>
> --- policy.sgml.orig 2005-01-19 01:10:37.000000000 +0100
> +++ policy.sgml 2005-01-19 01:13:05.000000000 +0100
> @@ -5392,13 +5392,17 @@
> <tag><tt>
> <item>cause the configuration to be reloaded if the
> service supports this, otherwise restart the
> - service.</item>
> + service,</item>
> +
> + <tag><tt>
> + <item><p>show the status of the service (either running
> + or dead).</item>
> </taglist>
I don't think this is a sufficient specification. We should make it
clear what status should display in the different case:
1) init script does not start a daemon
2.a) init script start a daemon which is running
2.b) init script start a daemon which is not running
3) init script start several daemons
4) init script was disabled in config
Cheers,
--
Bill. <email address hidden>
Imagine a large red swirl here.