Hello Paul!

20 Sep 19 20:11, you wrote to me:

 PH> On 18 Sep 2019 at 08:17p, Jeff Smith pondered and said...

 JS>> I am contining to have a problem with stale or undeleted busy
 JS>> files. I

 PH> [snip]

 JS>> Sep 18 00:42:01 FIDOPOLL Version 1.12 A43 2019/03/02
 JS>> Sep 18 00:42:01 Looking up address "1:3634/12" in nodelist
 JS>> Sep 18 00:42:01 Scanning 1:3634/12
 JS>> Sep 18 00:42:01 Queued 0 files (0 bytes) to 1:3634/12
 JS>> [...]
 JS>> Sep 18 00:42:01 R: NUL TIME Wed, 18 Sep 2019 01:42:01 -0400
 JS>> Sep 18 00:42:01 Info TIME Wed, 18 Sep 2019 01:42:01 -0400
 JS>> Sep 18 00:42:01 R: NUL VER binkd/1.1a-99/Linux binkp/1.1
 JS>> Sep 18 00:42:01 Mailer binkd/1.1a-99/Linux binkp/1.1
 JS>> Sep 18 00:42:01 R: ADR  1:3634/12@fidonet 1:3634/0@fidonet
 JS>> 1:123/0@fidonet 1:18/0@fidonet 1:1/120@fidonet 432:1/139@vkradio
 JS>>

 PH> did it hang there Jeff?

Yup. The above is where the log file ended. I have noticed that
there have been previous and subsequent connections to the same
node that completed succesfully

 PH> was this IPv4 or 6 ?

In this instance it was with a IPv4 only specification. Previously
I had Mystic setup to use either IPv specification for that node.


Jeff


--- Mystic v1.12 A43 (2019/03/02) GoldED+/LNX 1.1.5-b20170303