> #cp ext does not crash the stack, but is picked up as a signal to stop > the stack.
Sorry -- meant crash in this case that there is no explicit shutdown command (other than this somewhat obscure use of the external interrupt command). Thanks for the clarification. > My understanding is that from that point the stack does not > accept new connections but continues to run the open ones and give > them time to close. I suppose this might make sense to complete a > current ftp transfer or web transaction. > So it might make sense to have TCPIP understand a signal shutdown like > that. If the sessions don't close all before the signal expired, CP > will take the virtual machine down. Would work. I'll write a requirement for WAVV. Should be simple enough to implement -- the stack shutdown logic is already there in the external interrupt handler that is managing the #CP EXT response now; it'd just have to register for SIGNAL processing and branch to the existing shutdown routines when it gets the magic signal. Should have a draft ready later today. -- db
