From owner-freebsd-isdn Tue Jul 20 1: 5: 2 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from meloghost.melog.de (meloghost.melog.de [193.155.17.3]) by hub.freebsd.org (Postfix) with ESMTP id B9F9414F48 for ; Tue, 20 Jul 1999 01:04:51 -0700 (PDT) (envelope-from hf@Melog.DE) Received: from janus (janus.melog.de [193.155.17.21]) by meloghost.melog.de (8.9.3/8.9.3) with ESMTP id KAA08135; Tue, 20 Jul 1999 10:03:30 +0200 Message-Id: <4.2.0.58.19990720094640.00a89200@mail.saphirsc.de> X-Sender: hf@meloghost.melog.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 20 Jul 1999 10:00:20 +0200 To: hm@hcs.de From: Hauke Fath Subject: Re: Problems with callback setup Cc: freebsd-isdn@FreeBSD.ORG In-Reply-To: References: <4.2.0.58.19990719170219.00a4e8c0@mail.saphirsc.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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