> > > What reason would the rest of the "world" have to read rc.conf? It could
> > > only create a possible security risk.
> >
> > This is shabby reasoning. rc.conf contains public system configuration
> > data, which may need to be consumed by non-root processes.
>
> What kind of non-root program would need to consume rc.conf?
Anything that wants access to paramters stored there. Visualise eg. a
generic system monitoring script that checks the health of enabled
services; any daemon running in a sandbox. Even rc.pccard could be run
as non-root (modulo some changes to the way that ifconfig works).
The point being that rc.conf is currently a public database, and until
we have a better mechanism for managing parameter storage, it needs to
stay that way.
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ [EMAIL PROTECTED]
\\ -- Joseph Merrick \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
