Restarting services

Vasil Dimov vd at
Mon Sep 25 03:01:45 PDT 2006

On Mon, Sep 25, 2006 at 11:47:46AM +0200, Erwin Van de Velde wrote:
> On Monday 25 September 2006 11:26, Vasil Dimov wrote:
> > IMHO in this case the administrator should be changed,
> > not the way ports operate. Building idiot-proof system is impossible and
> > leads to the:
> >
> > Shaw's Principle:
> >         Build a system that even a fool can use, and only a fool will
> > want to use it.
> This is not about being idiot-proof but being handy to use. It also reduces 
> service downtime by immediately restarting the service after update instead 
> of waiting for the administrator to restart it.

I think that implementing this feature the right way would be too
complex and would bring too little benefit. By "right way" I mean that
a given service should be started upon installation only if it was
actually stopped during the upgrade process.

Ofcourse if someone thinks that it is worth implementing I would be
happy to be asked
"service xyz was stopped during upgrade, do you want to start it now?" [y]

One could always minimize downtime by doing
portupgrade xyz && /usr/local/etc/rc.d/xyz start

Vasil Dimov
gro.DSBeerF at dv
If you're happy, you're successful.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 155 bytes
Desc: not available
Url :

More information about the freebsd-ports mailing list