cvs commit: ports/sysutils/bsdstats Makefile pkg-install
kris at obsecurity.org
Fri May 4 00:06:44 UTC 2007
On Thu, May 03, 2007 at 07:33:41PM -0300, Marc G. Fournier wrote:
> --On Saturday, April 28, 2007 15:21:32 -0400 Kris Kennaway
> <kris at obsecurity.org> wrote:
> > On Sat, Apr 28, 2007 at 07:12:31PM +0000, Marc G. Fournier wrote:
> >> scrappy 2007-04-28 19:12:31 UTC
> >> FreeBSD ports repository
> >> Modified files:
> >> sysutils/bsdstats Makefile pkg-install
> >> Log:
> >> By popular request, I've added a bsdstats.sh script to etc/rc.d so that
> >> it can be enabled to run on reboot (ie. for laptops, office computers, etc)
> >> since not everyone runs a server 24/7 ...
> >> I've added to pkg-install a yesno question as to whether it should be
> >> enabled on reboot, seperate from the monthly periodic run ...
> > Interactive pkg_installs are the work of the devil :( Think what
> > happens when a user tries to add your package from sysinstall. Hint:
> > the TTY used by pkg_add is over on another VTY.
> Hrmmm ... hadn't thought about sysinstall :( But, what behaviour should happen
> if someone installs via sysinstall? Auto-enabled? Then again, if someone does
> go to the trouble of installing it in the first place, even interactively,
> would it make more sense to just get rid of the interactive altogether and have
> it auto-enable, and let them know how to disable?
> Would it make sense / be acceptable to have it auto-enable the stats if someone
> installs, but leave the 'extra reports' disabled unless they manually modify
> /etc/periodic.conf to enable them? That sounds to be like it would be the
> least offensive, but a 'second opinion' would be appreciated ...
Usually packages need to be enabled explicitly in rc.conf.
More information about the cvs-all