From 631c2d5af9d613757a99ead225bf129362e4e29e Mon Sep 17 00:00:00 2001 From: Gerrit Pape Date: Thu, 29 Jun 2006 07:52:00 +0000 Subject: * doc/benefits.html: typo; wording. 1.6.0.. --- doc/benefits.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/benefits.html b/doc/benefits.html index b55d48c..d2b9f47 100644 --- a/doc/benefits.html +++ b/doc/benefits.html @@ -33,7 +33,7 @@ By default a service is defined to be up, that means, if the service daemon dies, it will be restarted. Of course you can tell runsv otherwise.

-This reliable interface to control daemons and supervisors obsolete +This reliable interface to control daemons and supervisors obsoletes pid-guessing programs, such as pidof, killall, start-stop-daemon, which, due to guessing, are prone to failures by design. @@ -47,7 +47,7 @@ resource limits, open file descriptors, and controlling terminals.

You don't necessarily have that with sysv init scripts for example. It requires a carefully written init script that reliably cleans up and sets -the initial process state before starting the service daemon. +the process state before starting the service daemon. This adds even more complexity to the init script in comparison with a run script used by runit. Many of today's init scripts don't provide a clean process state, here is @@ -146,7 +146,7 @@ the default sysvinit.

-Stage 2 already is packaging friendly: +Stage 2 is packaging friendly: all a software package that provides a service needs to do is to include a service directory in the package, and to provide a symbolic link to this directory in /var/service/. -- cgit 1.4.1