On Wed, 7 Oct 2009, Xin LI wrote:
> Wesley Shields wrote:
> > On Sun, Oct 04, 2009 at 12:30:55PM -0700, Doug Barton wrote:
> >> Alex Trull wrote:
> >>> Hi all,
> >>>
> >>> I realised that because portupgrade/portmaster don't always
> >>> cleanly restart processes that have died due to being
> >>> u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wesley Shields wrote:
> On Sun, Oct 04, 2009 at 12:30:55PM -0700, Doug Barton wrote:
>> Alex Trull wrote:
>>> Hi all,
>>>
>>> I realised that because portupgrade/portmaster don't always
>>> cleanly restart processes that have died due to being
>>> up
On Sun, 4 Oct 2009 15:11:18 +0100
Alex Trull wrote:
> Hi all,
>
> I realised that because portupgrade/portmaster don't always
> cleanly restart processes that have died due to being
> upgraded (mysqld, often!) that this was something I wanted
> to fix.
You can configure portupgrade (and FWIW
On Sun, Oct 04, 2009 at 12:30:55PM -0700, Doug Barton wrote:
> Alex Trull wrote:
> > Hi all,
> >
> > I realised that because portupgrade/portmaster don't always
> > cleanly restart processes that have died due to being
> > upgraded (mysqld, often!) that this was something I wanted
> > to fix.
>
Alex Trull wrote:
> Hi all,
>
> I realised that because portupgrade/portmaster don't always
> cleanly restart processes that have died due to being
> upgraded (mysqld, often!) that this was something I wanted
> to fix.
I can't speak to portupgrade, however for portmaster there is no such
facil
Hi all,
I realised that because portupgrade/portmaster don't always
cleanly restart processes that have died due to being
upgraded (mysqld, often!) that this was something I wanted
to fix.
However, I'd seen the daemontools and wasn't a fan - too
much to configure with weird directories and so
6 matches
Mail list logo