[Info-vax] TCPIP tying up system

R.A.Omond Roy.Omond at BlueBubble.UK.Com
Sun Nov 28 17:58:10 EST 2010


On 28/11/2010 16:22, JF Mezei wrote:
> [...snip...]
>
> 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 ?
>
> 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.

Oh for goodness sake, JF ... from the OP:

"Today, it tied things up so bad I had to do CTRL-P and reboot.  I
couldn't access any active sessions and couldn't log in from elsewhere."

Phillip screwed up.  He had to Control-P and *reboot*.  That was, ahem,
shall we say "less than optimal".  If my customers had done that, I'd
be cursing under my breath.

And yes, crash dump analysis is what I do.



More information about the Info-vax mailing list