Date: Tue, 20 Jul 1999 10:00:20 +0200 From: Hauke Fath <hf@Melog.DE> To: hm@hcs.de Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: Problems with callback setup Message-ID: <4.2.0.58.19990720094640.00a89200@mail.saphirsc.de> In-Reply-To: <m116Hfu-0001b7C@hcswork.hcs.de> References: <4.2.0.58.19990719170219.00a4e8c0@mail.saphirsc.de>
next in thread | previous in thread | raw e-mail | index | archive | help
At 19:58 19.07.99 +0200, Hellmuth Michaelis wrote:
> >From the keyboard of Hauke Fath:
>
> > >Yes, isdnd is fail-safe, at least in the alpha version. In the beta
> version,
> > >it obviously got more robust, so i removed the fail-safe code :-)))
> >
> > Hum... Makes it too easy for my liking to cut the branch I am sitting on.
>
>It cooled down quite a bit, so:
>
>Did you saw the triple smiley ?
Yep. But my thoughts were still on the underlying problem. ;)
>Isdnd's fail-safeness has/was not changed although its got quite more
>robust over the time. In fact, some isdnd's have an uptime of months here
>and are only killed to upgrade them. Remember, i4b is still beta and we
>are still removing that kind of bugs here and there, where one thinks
>"how could this stuff even run before ... ?".
I wasn't referring to bugs here. From what little understanding of the
syslog data I have, isdnd's state machine detected an illegal state, and,
instead of cleaning up and starting from scratch, decided to quit. Thus,
you may lose connectivity permanently because of a failure that was only
temporary. Can you say "DOS"?
Now that I know about the problem I could easily put a wrapper around isdnd
and restart it when it dies. But there may be situations when quitting is
the only sensible thing to do (imagine looping on dial-out and the
resulting costs...) which only the daemon itself can detect and deal with
reasonably.
hauke
--
Hauke Fath Saphir Software GmbH
D-69115 Heidelberg
hf@SaphirSC.DE Ruf +49-6221-13866-35, Fax -21
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.2.0.58.19990720094640.00a89200>