[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: iatuh misbehaviour

To: ircd-users@xxxxxxx
Subject: Re: iatuh misbehaviour
From: Michael Neumayer <Michael.Neumayer@xxxxxxxxxxxxxxxxxxxx>
Date: Wed, 10 Feb 1999 13:30:37 +0100
Delivered-to: ircd-users-out@irc.org
Delivered-to: ircd-users@irc.org
In-reply-to: <19990209083225.B323@stealth.net>; from Christophe Kalt on Tue, Feb 09, 1999 at 08:32:26AM -0500
Mail-followup-to: ircd-users@irc.org
References: <19990209002007.G18082@helpdesk.rus.uni-stuttgart.de> <19990209083225.B323@stealth.net>

On Tue, Feb 09, 1999 at 08:32:26AM -0500, Christophe Kalt wrote:
> iauth will only be restarted one per minute (or something
> similar) to avoid forking madness.

How to avoid "Eumel madness"?

> it is imperative that iauth be stable, if it crashes we
> should really look into it.

No core file. Dunno what's wrong. Last time automatic restart didn't work.
First manual restart neither. Second succeeded and stable now. Bleh.

> However, i have been trying for some time to change the
> current behaviour to avoid the situation you describe.

Go go go! ;)

-- 
+----------------------------------------------------------------------------+
|    Michael 'Eumel' Neumayer     <Michael.Neumayer@xxxxxxxxxxxxxxxxxxxx>    |
|    Eumel@IRC             ! LinuX inside !             pgp-key available    |
+----------------------------------------------------------------------------+

Follow-Ups:
- Re: iatuh misbehaviour
  - From: Christophe Kalt

References:
- iatuh misbehaviour
  - From: Michael Neumayer
- Re: iatuh misbehaviour
  - From: Christophe Kalt

Prev by Date: Re: PING/PONG
Next by Date: Re: Current PING/PONG implementation to violate the RFC
Previous by thread: Re: iatuh misbehaviour
Next by thread: Re: iatuh misbehaviour
Index(es):
- Date
- Thread