There, I got your attention :)
Recently FidoPoll seems to be leaving BSY files laying around, I think I
might have tracked it down, but not sure. It seems to happen when it has
a problem connecting to another system. In the last day it attempted to connect 3 times and 2 of those 3 times.
This morning after a fresh start (fidopoll killbusy), fidopoll ran on
it's own at 7:27, it got one poll in, and then it timed out on the next node and then the rest are all busy. BSY files are created and then fidopoll won't run again until I clear them.
Sep 21 07:27:22 Recv: EOB
Sep 21 07:27:22 State RxS:1 TxS:4 HH:1 NH:0
Sep 21 07:27:22 Session complete (0 sent, 1 rcvd, 0 skip)
Sep 21 07:27:22 Polling BINKP node 618:200/1
Sep 21 07:27:22 Connecting to curmudge.hopto.org <<<<<<<<<<<<<<
Sep 21 07:29:29 Unable to connect
Avon wrote to bl00d <=-
On 09/21/16, bl00d pondered and said...
That's correct it creates them for all nodes while a process is
running, removing them for each echonode once it has called it. Are you using fidopoll send or forced out of interest?
If the fidopoll session is not ending normally then it's usual for the .bsy files to remain against the other nodes.
They key to progressing this would be to isolate the system causing you the polling issues. Is there mail waiting to be sent to it? Could you
Sep 21 07:27:22 Polling BINKP node 618:200/1
Sep 21 07:27:22 Connecting to curmudge.hopto.org <<<<<<<<<<<<<<
Sep 21 07:29:29 Unable to connect
That's a heck of a long time before timeout, what do you have your settings set to for timeout for this node?
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 2 |
Nodes: | 8 (0 / 8) |
Uptime: | 135:38:42 |
Calls: | 2,128 |
Calls today: | 1 |
Files: | 11,149 |
D/L today: |
27 files (9,988K bytes) |
Messages: | 951,049 |