[Info-vax] TCPIP tying up system

[Bob Koehler]

In article <4cf436f7$0$7549$c3e8da3$40d4fd75 at news.astraweb.com>, JF Mezei <jfmezei.spamnot at vaxination.ca> writes:
> 
> SET PROC/PRIO=16 when you create a session  is far simpler and lets you
> do interactive stuff while some hackers try to get into your system.

   Unless your system is hung up at elevated IPL.  Something I used to
   get into with faulty custom peripherals, failing VAX components,
   and/or buggy device drivers.

   Since the SWAPPER is priority 16 and seems to be a good bit of the
   OP's load, I'd try something higher.  On systems wiht several
   real-time processes (higher than 16) I used to log into a privileged
   account with a default priority of 31 and turn it down at the begining
   of LOGIN.COM.  If the system was having performance problems, then
   logging in /NOCOMMAND would get me in higher than any of our
   real-time processes so I could get some quick analysis.

   For that, everyone else was paying for my logins to get through
   SYLOGIN and start LOGIN.COM while still at 31.  I made sure there
   wasn't much in there.