I don't really like things that just "go" -- there are already examples
of this in the Linux world where various services are enabled on a stock
system, without the user really knowing about them (or needing them).
IMHO it would be better if daemons do not run automatically, but rather
require the system administrator to enable them.

I've been looking at the apache pkg (in hopes of upgrading to using the
pkg instead of a locally maintained copy) and these feelings have only
been made stronger.  The apache pkg installs a default configuration on
the system (in /usr/pkg/etc/httpd/httpd.conf), which in combination with
the startup script would publish files openly.

I would feel better about just providing a sample configuration file that
the administrator can modigy and install next to the other host-specific
somewhere in /etc (e.g. in /etc/httpd) and the server should default to
that location for its configuration (so it would fail to start without
intentional configuration).

+ Kim


thorpej@shagadelic.org (Jason R Thorpe) writes:

| On Mon, Mar 13, 2000 at 09:08:32AM +1100, Luke Mewburn wrote:
| 
|  > c) Add support for /etc/rc.pkg.d, and ensure that that directory
|  >    is created during installation.
|  >    This is for packages. After a package installation a user should
|  >    copy the script from /usr/pkg/share/examples/rc.d/ to /etc/rc.pkg.d
|  >    to enable the startup.
| 
| This is a lose.  Once the user installs a package, he shouldn't have
| to copy stuff around to make it go.  I think this is going to be a serious
| negative for our pkg system.
| 
| At the very least, this change should be VERY CEARLY AND LOUDLY
| documented in our packages documentation.
| 
| -- 
|         -- Jason R. Thorpe <thorpej@shagadelic.org>
-- 
Kimmo Suominen
kim@tac.nyc.ny.us