On Sun, Sep 12, 2010 at 09:46:02AM +0300, Ion-Mihai Tetcu wrote: > On Sun, 12 Sep 2010 06:45:47 +0800 Denny Lin <[email protected]> > wrote: > > On Sat, Sep 11, 2010 at 11:35:43PM +0200, Torfinn Ingolfsen wrote: > > > On Sat, Sep 11, 2010 at 4:33 PM, Ion-Mihai Tetcu <[email protected]> > > > wrote:
> > > > This 'stop the service before we install' seems to be a new > > > > fashion, usually unneeded/disruptive. > > > > IMO this should only happen when it's really needed, and with > > > > some big warning printed. > > > > > > > > > > And perhaps with a restart service attempt afterwards? (maybe > > > interactive as in "do you want me to restart the service y/n?") > > > Just my 0.02 euros. > > > > How about knobs like WITH_STOP_SERVICE and WITH_START_SERVICE for > > users who wish to avoid the y/n questions? > > We have a standard policy of not auto-starting anything. > We really don't want a service to be stated automatically after install > (think: I installed this today, I'll configure it how I need it > tomorrow, then start the service). > And you can't really know if it's a new install or an upgrade. Is this really a problem? It seems to me that the presence of 'dhcpd_enable="YES"' in /etc/rc.conf (or whatever similar entry is used for a given service) should answer the question of whether some service should be started after an upgrade. I always restart any services after an upgrade. The reason being, if by chance something does go wrong, I want to know about it at that time, while the server is maintenance (when I can be reasonably sure of the cause), not at some random time in the future (when someone will have to troubleshoot the problem -- on a server that is supposed to be live). -- greg byshenk - [email protected] - Leiden, NL _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
