Go directly to ST_STOPPED when a TerminateReq is
received and after the TerminateAck is sent (as per rfc1661) rather than to ST_STOPPING. Going to ST_STOPPING will leave us in a state where we're waiting for the other side to do something - not a good idea, especially as the client side sends a TerminateReq then exits on idle timeout.
This commit is contained in:
parent
0d8fb00071
commit
ceb1cfa497
@ -17,7 +17,7 @@
|
||||
* IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
|
||||
* WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
|
||||
*
|
||||
* $Id: fsm.c,v 1.9 1997/02/22 16:10:13 peter Exp $
|
||||
* $Id: fsm.c,v 1.10 1997/05/10 01:22:10 brian Exp $
|
||||
*
|
||||
* TODO:
|
||||
* o Refer loglevel for log output
|
||||
@ -521,10 +521,10 @@ struct mbuf *bp;
|
||||
NewState(fp, ST_REQSENT);
|
||||
break;
|
||||
case ST_OPENED:
|
||||
(fp->LayerDown)(fp);
|
||||
(fp->LayerFinish)(fp);
|
||||
/* Zero Restart counter */
|
||||
(fp->SendTerminateAck)(fp);
|
||||
NewState(fp, ST_STOPPING);
|
||||
NewState(fp, ST_STOPPED);
|
||||
break;
|
||||
}
|
||||
pfree(bp);
|
||||
|
Loading…
x
Reference in New Issue
Block a user