That is what happens. I have 32 job slots, and usually it takes less than two weeks to
fill up. Unless I happen to log in in between and kill the jobs.
Groet,
Wilm
(Verstuurd vanaf mijn telefoon, dus wat korter dan gewoonlijk.)
(Sent from my phone, so a bit more compact than usual)
Op 13 sep. 2022 om 12:00 heeft Johnny Billquist
<bqt(a)softjar.se> het volgende geschreven:
Are you saying that even though the DECnet connections are finished, there are processes
that stay around forever? That seems wrong.
Johnny
On 2022-09-13 10:06, Wilm Boerhout wrote:
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*
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt(a)softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se