Vasil Dimov wrote:
> On Tue, Sep 26, 2006 at 10:15:49AM +0400, Sergey Matveychuk wrote:
>> Vasil Dimov wrote:
>>> One could always minimize downtime by doing
>>> portupgrade xyz && /usr/local/etc/rc.d/xyz start
>>>
>> You should not do it with portupgrade. Just add the lines in pkgtools.conf:
>>
>>
On Tue, Sep 26, 2006 at 10:15:49AM +0400, Sergey Matveychuk wrote:
> Vasil Dimov wrote:
> >
> > One could always minimize downtime by doing
> > portupgrade xyz && /usr/local/etc/rc.d/xyz start
> >
>
> You should not do it with portupgrade. Just add the lines in pkgtools.conf:
>
> AFTERINSTALL
Vasil Dimov wrote:
>
> One could always minimize downtime by doing
> portupgrade xyz && /usr/local/etc/rc.d/xyz start
>
You should not do it with portupgrade. Just add the lines in pkgtools.conf:
AFTERINSTALL = {
'*' => proc { |origin|
cmd_start_rc(origin)
},
}
--
Dixi.
S
--On Monday, September 25, 2006 11:47:46 +0200 Erwin Van de Velde
<[EMAIL PROTECTED]> 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
On Mon, 25 Sep 2006 10:35:15 +0200
Erwin Van de Velde <[EMAIL PROTECTED]> wrote:
> Dear all,
>
> Almost every port containing a service stops the service before updating but
> does not restart it afterwards. I was wondering how difficult it can be to
> restart the updated service after installi
On 9/25/06, Vasil Dimov <[EMAIL PROTECTED]> wrote:
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 i
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 Princi
> Well each server/service would need a program to check the syntax of the
> current config file to ensure that it will work.
> Otherwise, imho, you could only try and error which is not a clean
> solution.
You could also warn when big configuration changes happen and not restart the
service in t
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
> w
On Mon, Sep 25, 2006 at 10:35:15AM +0200, Erwin Van de Velde wrote:
[...]
> In my opinion, it
> would be less error-prone than hoping for the administrator to remember
> restarting all updated services...
IMHO in this case the administrator should be changed,
not the way ports operate. Building
Rene Ladan wrote:
> 2006/9/25, Erwin Van de Velde <[EMAIL PROTECTED]>:
>> Dear all,
>>
>> Almost every port containing a service stops the service before
>> updating but
>> does not restart it afterwards. I was wondering how difficult it can
>> be to
>> restart the updated service after installing
2006/9/25, Erwin Van de Velde <[EMAIL PROTECTED]>:
Dear all,
Almost every port containing a service stops the service before updating but
does not restart it afterwards. I was wondering how difficult it can be to
restart the updated service after installing the files? In my opinion, it
would be
12 matches
Mail list logo