[Info-vax] TCPIP tying up system

Bob Koehler koehler at eisner.nospam.encompasserve.org
Mon Nov 29 15:45:55 EST 2010


In article <4cf281c0$0$17480$c3e8da3$b280bf18 at news.astraweb.com>, JF Mezei <jfmezei.spamnot at vaxination.ca> writes:
> John Wallace wrote:
> 
>> While we await the crash dump info, would it be appropriate, for the
>> benefit of other readers who may one day find themselves in a similar
>> situation where a crash dump provides answers rather than the present
>> guesswork and speculation,
> 
> 
> Excuse me ?
> 
> Why a crash dump because you CPU reaches 100% and you can't issue
> commands because thge TCPIP processes that consume CPU have higher
> priority than normal interactivce processes ?

   Because you can force a crash dump from the console without entering
   and DCL commands.  Then you have the data you need to find out how
   you got there and do something about it before it happens again.

> 
> There is no "crash" here, just piss poor implementation of TCPIP
> Services which grants itself too high a priority and will bog down a system.
> 
> Once the attack is ended, the system returns to normal. Teling people to
>  get a crash dump on VMS like that is like asking Windows users to ALT
> CTRL DEL their system and re-install Windows because their ADSL modem is
> not performing well.

   Nope.  When you reboot Windows, you still have no idea how it got
   so messed up.




More information about the Info-vax mailing list