This new version squashes a bug reported by Dan Richter that causes Unsecured session traffic to get lumped in with the last good Node processed. These transfers will now show as "Unsecured" node traffic on the report. So far I have been unable to determine a reliable way to ID Unsecure Nodes in the log but will look into this further! New archive should be in your inbound and:
I guess the real solution would be to secure the connection I have
with that node. It would seem to alleviate a lot of issues. I'll work
on it. :)
As I stated in one of the emails, you are an awesome developer. Keep
up the good work! :) It is very much appreciated.
Hi Avon,
This new version squashes a bug reported by Dan Richter that causes Unsecured session traffic to get lumped in with the last good Node
This new version squashes a bug reported by Dan Richter that causes Unsecured session traffic to get lumped in with the last good Node processed. These transfers will now show as "Unsecured" node traffic on the report. So far I have been unable to determine a reliable way to ID Unsecure Nodes in the log but will look into this further! New archive should be in your inbound and:
determine a reliable way to ID Unsecure Nodes in the log but willI am more than happy to work with you on some logging text if it will
help you identify certain things. I'm very pleased to know someone
has made such a utility! :)
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 31 |
Nodes: | 8 (0 / 8) |
Uptime: | 163:44:59 |
Calls: | 2,076 |
Calls today: | 2 |
Files: | 11,137 |
Messages: | 947,148 |