On Wed, 24 Apr 2002, paul beard wrote:

> > It did on my machine when I started it up.  And all my 1.5.x machines
> > have behaved that way as well.  If you look at the code, (either once
> > you've load /etc/rc.d on you machine, or in the repository) you will
> > see a pre-command to start that checks if a key file exists, and calls
> > a keygen routine if it doesn't.
>
> well, that's very nice but hardly obvious: I assumed setting
> various options to YES just made them run, not set up things like
> keyfiles. perhaps some one-line comments in rc.conf would be
> helpful: options commented out, of course, but some idea of what
> will happen if they're enabled.

There's some documentation in /etc/defaults/rc.conf, which has the default
settings for everything. i.e. all of the foo=NO settings that you override
in /etc/rc.conf.

> I seem to have missed where a lot of this stuff is documented.

At the moment, it's documented in the source. :-(

In general rc.d scripts do what's needed to make the service work. Making
made-once config files (keys, etc.) certainly fits. Especially for ssh, as
we've added different host key types (DSA v2, RSA v2) over time.

Documenting all of the little twists like that would be a lot of work. :-(

Take care,

Bill