[Info-vax] TCPIP tying up system

[Jan-Erik Soderholm]

On 2010-11-28 17:26, JF Mezei wrote:
> Richard B. Gilbert wrote:
>
>>>> 24060604 TCPIP$SMT_BG416 COM     11      152   0 00:00:18.90      3233    240  N
>
>> It would be a lot of work, but you could identify the addresses sending
>> the junk and block them.  Or, you might try using an ISP such as Comcast
>> that blocks 99.44% of the crud.
>
> I do not think that the SMTP receiver creates processes with the above
> names. But I am not sure.
>
> I had my smtp service limit set to 3.
>
> BTW, one way to find out is to
>
> SHOW PROC/CONT/ID=24060604  This will give you the image being executed.
>
>

SHOW SYSTEM/IAMGES will get you all currently executing images in
one listing, at least on a 8.2/8.3 system. I've no idea if that
is/was available on 7.x.

On my system, receving a mail creates :

0000165C TCPIP$S_BG43319 LEF  8  392 0 00:00:00.14   991  543  N
          DSA10:[SYS0.SYSCOMMON.][SYSEXE]TCPIP$SMTP_RECEIVER.EXE

So, yes, I think the TCPIP$SMT_BG416 above at least *can* be
a SMTP process.

The length of the "S" or "SMT" part is probably depending on
the length of the BG416 or BG43319 part.