On Wed, Feb 09, 2000 at 10:00:57AM +0100, [EMAIL PROTECTED] wrote:
> > I've had servers
> > in production that start crashing and alert the user. Then I go in with
> > ProcessTop and, without restarting, work around the problem. The user
> > is impressed.
>
> So do I! And I was already impressed
> I've had servers
> in production that start crashing and alert the user. Then I go in with
> ProcessTop and, without restarting, work around the problem. The user
> is impressed.
So do I! And I was already impressed by ProcessTop itself. Just to mention it in the
talk (and because of my curi
On Tue, Feb 08, 2000 at 05:57:18PM -0500, [EMAIL PROTECTED] wrote:
> > "JNP" == Joshua N Pritikin <[EMAIL PROTECTED]> writes:
> JNP> Actually, turning errors into warnings is a *feature*. I've had
> JNP> servers in production that start crashing and alert the user.
> JNP> Then I go in w
> "JNP" == Joshua N Pritikin <[EMAIL PROTECTED]> writes:
JNP> Actually, turning errors into warnings is a *feature*. I've had
JNP> servers in production that start crashing and alert the user.
JNP> Then I go in with ProcessTop and, without restarting, work around
JNP> the problem. T
On Tue, Feb 08, 2000 at 05:25:33PM -0500, [EMAIL PROTECTED] wrote:
> well, since we have been on a feature frenzy i thought i would toss in
> this one to the sharks.
>
> when i have made a serious problem in setting up a callback, event
> generates errors in a loop. i know i should use a $Event::
well, since we have been on a feature frenzy i thought i would toss in
this one to the sharks.
when i have made a serious problem in setting up a callback, event
generates errors in a loop. i know i should use a $Event::DIED handler
to deal with this but i think it should wrok better by default.
