[Info-vax] Reverse telnet printers (TNAxxxx:) owned by non-existent process

[Grant Taylor]

On 6/1/21 10:22 AM, Scott Snadow wrote:
> But that's a hack.  I'd much rather prevent the problem from occurring 
> in the first place.  Any ideas on what causes this and/or how to 
> stop it?

I'm just lobbing this out there.

Is there any chance that the problem is associated with timing and how 
quickly print jobs are sent to the TNAs?  As in if jobs are sent close 
enough together / back to back that the connection(s) / print jobs 
(maybe on the printer's end) are causing state to be wrong?  E.g. two 
print jobs close enough together / back to back that the second one ends 
up re-using the first one's established connection?

Where I'm going with this is if the second one tries to clear the 
connection it thinks it established, it probably can't because the data 
is wrong.  Similarly the first print job can't clear it's connection 
because it's in use by the second print job.

I don't know.  I'm just thinking out loud.

If this, or something timing related, is close to the problem, I'd think 
that you could probably reproduce this on demand once you figure out the 
problem criteria.



-- 
Grant. . . .
unix || die