BoF Protocol

[Mark Brown]

On Wed, Jun 13, 2007 at 04:56:23PM +0200, Michael Biebl wrote:

> Can you give some examples where a daemon can't be started by default?

> I can only think of the two atm:
> 1.) Missing configuration data

That was pretty much the main one.

> - Easy solution: Check for the configuration, e.g. a missing config
> file are missing setting in a config file. In that case, exit and
> (optionally, probably based on the VERBOSE setting) give a warning
> message.

Depending on the particular reason that there is a problem this can be
very difficult to do and obviously it can decay into something close
enough to the checks you're trying to avoid to be indistinguishable.

-- 
"You grabbed my hand and we fell into it, like a daydream - or a fever."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 307 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/initscripts-ng-devel/attachments/20070613/eb98a1f5/attachment.pgp