Subj : Re: callip.nl
To   : Stas Mishchenkov
From : Nodelist Police Commissioner
Date : Sat Jan 29 2022 12:20:40

Hello Stas,

On 2022-01-29 12:02:08, you wrote to me:

 NPC>> For instance when I tested a net:

 NPC>> 2022-01-28 14:16:17 Calling 39:170/0
 NPC>> 2022-01-28 14:16:17 datenbahn.dd-dns.de:24554
 NPC>> 2022-01-28 14:16:17  31.19.183.44 - Error Connection timed out
 NPC>> 2022-01-28 14:16:17No such AKA.
 NPC>> 2022-01-28 14:16:17
 NPC>> 2022-01-28 14:16:17 Calling 39:170/5834
 NPC>> 2022-01-28 14:16:17 datenbahn.dd-dns.de:24554
 NPC>> 2022-01-28 14:16:17No such AKA.
 NPC>> 2022-01-28 14:16:17  31.19.183.44 - Error Connection timed out

 NPC>> Sometimes when there is a "connection timed out", there is also a "No
 NPC>> such AKA", but not for all the timeouts?

 SM> That's why:
 SM> [fido@brorabbit bin]$ host datenbahn.dd-dns.de
 SM> datenbahn.dd-dns.de has address 31.17.199.89
 SM> datenbahn.dd-dns.de has address 31.19.183.44

Ok, understood. But it should be made more clear in the logs.

 NPC>> What I would like is milliseconds in the log. ;)

 SM> I will made it,

Thanks! ;)

 SM> but it doesn't make much sense.

Sometimes it is usefull information.

 SM> The script is multi-threaded and each session writes the entire result
 SM> to the log at once, and not in stages, like mailers.

But it could still be possible that they get mixed up, when two threads start writing at exactly the same time? If so maybe you start each logline with the nodenumber?

 NPC>> And also the system and sysop name, for the tested systems. Or maybe
 NPC>> even what is reported back in the SYS and ZYZ fields.

 SM> I will made it.

Thanks!

Regards, NPC.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: NPC Station (2:280/464)

.