It's apparently a programming mistake in the source code from diald 0.99.2
up.  The fix has been posted to the list in the past (I could not find it
originally, too).  Hope Sagami fixes it in the RPM
(http://member.nifty.ne.jp/sagami/linux/rpm.htm), or is it already fixed
there?
Petr
----- Original Message -----
From: "Mark Sawle" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 17, 2000 12:51 AM
Subject: Sticking in CLOSE state


> I upgraded to diald 0.99.2 today and immediately discovered a problem
> whereby it would get stuck in the CLOSE state when the ISDN connection
> died.
>
> I tracked the problem down to trans_CLOSE in fsm.c which reads:
>
> void trans_CLOSE(void)
> {
>     if (request_up || request_down)
> GOTO(STATE_DOWN); /* STATE_DOWN handles the link-up-request */
>     if (no_redial_delay == 1) {
> no_redial_delay = 0;
> if (two_way)
>   GOTO(STATE_DOWN);
>     }
> }
>
> Removing the "if (two_way)" line fixed the problem, i.e. restoring the
> function to its 0.99.1 definition.
>
> --
> Mark Sawle                  | [EMAIL PROTECTED]
> Robinson College, Cambridge | [EMAIL PROTECTED]
>

----- Original Message -----
From: "Tim Coleman" <[EMAIL PROTECTED]>
To: "Petr Gruz" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, February 09, 2000 8:57 PM
Subject: Re: Diald 0.99.3 won't redial


> On Tue, Feb 08, 2000 at 12:53:18AM +0900, Petr Gruz wrote:
> > Hi,
> > When the modem of my provider unexpectedly hangs up Diald 0.99.3 would
not
> > redial even in the restrict up mode neither react to trigger packets
anymore
> > :-(  Needs to be restarted to behave normally again ...  I did not have
such
> > a problem with the same config and Diald 0.99.1
>
> This is the problem that I reported last week.
> I'm not sure what the status of it is.
>
> Tim
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
>



-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to