I have tried to keep up with the patches, also those advertised on this
list.
And it is not only netmapper that knocks on my door.
W
From: Keith Halewood <Keith.Halewood(a)pitbulluk.org>
Sent: Tuesday, September 13, 2022 11:00 AM
To: The Hobbyist DECnet mailing list <hecnet(a)lists.dfupdate.se>
Subject: [HECnet] Re: RSTS DECnet config question
I have two RSTS 10.1L nodes on HECnet and they see netmapper activity
regularly. I've not had any issues with job slots running out.
Did DECnet patching take place? Otherwise, it doesn't seem to be netmapper
causing this.
Keith
From: Wilm Boerhout [mailto:wboerhout@gmail.com]
Sent: 13 September 2022 09:06
To: hecnet(a)lists.dfupdate.se <mailto:hecnet@lists.dfupdate.se>
Subject: [HECnet] RSTS DECnet config question
Hail all you RSTS buffs!
One of my nodes (PIRSTS) is running RSTS V10.1L and DECnet V4.1
Ever since I am on HECnet, I have observed that job slots are filled over
time with jobs under the DECnet account [29,206] in HB state, up to the
point that the job max is reached, and I cannot log in anymore.
My working hypothesis is that the polling processes (for HECnet mapping and
other inquiring minds - you know who you are) keep creating new jobs,
instead of reusing old ones.
Is there a way to tell DECnet/E that it should not keep jobs in HB state,
but log them out after use? Or reuse existing jobs on incoming connection
requests? On DECnet/VMS there are timer and other logicals that steer this
behavior.
Running a daily kill job seems, well, overkill.
Thanks,
Wilm