Subj : callip.nl To : Nodelist Police Commissioner From : Stas Mishchenkov Date : Fri Feb 04 2022 20:44:36 Hi, Nodelist! 02 фев 22 13:16, Nodelist Police Commissioner -> Stas Mishchenkov: NPC> I've had some time to think about this. I don't like the fact it NPC> "calls home" on every invocation! It shouldn't act like spyware where NPC> the user has no control over it. How can we talk about spyware in case of open source? ;) NPC> Maybe you could replace it with an option like for instance NPC> youtube-dl has: NPC> -U, --update Update this program to latest version. Make sure that you NPC> have sufficient permissions (run with sudo if needed) NPC> Which can be used on it's own, without doing anything else. And only NPC> checks for updates when this option is specificly used! Changed to: [fido@brorabbit perl]$ ./callip.pl Calls the specified nodes by the binkp protocol, using connect information from the nodelist. Usage: ./callip.pl [options] nodelist_file_name ~~~~~ -f,--fnode address - address of node to call. Optional. -z,--zone number - number of zone to test all nodes. Optional. -r,--region number - number of region to test all nodes. Optional. -n,--net network - number of network to test all nodes, i.e. 460. Optional. If you do not specify anything, then the check will pass through the entire nodelist. -l,--log log_file_name - file name of log file -a,--aka address - the fido address from which to make calls. Optional. default is '2:9999/9999.9999'. -c,--config - Configuration file name. Command line options owerrides it. Optional. Not needed by default. Use command callip.pl -e > callip.conf to create a new one -e,--export - export configuration end exit. -u,--update - How to update programm. Optional. =a - auto. Check for a new version, download and update. =d - download. Checks for a new version and download the update to a new file. =w - warn. Checks for a new version and warn the sysop. Default. =n - no. Do nothing. NPC>>> Btw: If you use '-a node' maybe the script could use the values NPC>>> from the nodelist for the SYS, ZYZ, and LOC info sent? Now it still NPC>>> says: Now it may be configured. NPC>>> - 29 Jan 12:28:15 [17842] SYS linux NPC>>> - 29 Jan 12:28:15 [17842] ZYZ Evil Robot NPC>>> - 29 Jan 12:28:15 [17842] LOC Sinferopol, Crimea NPC> Btw: Does the binkp protocol require that you send these, or can a valid NPC> connection be made without them? A valid connection may be made without them. NPC>>> Or maybe these values could be given on the command line too? Like: NPC>>> -a 2:280/464,system,sysop,location SM>> It turns out too much to write on the command line. I did better - an SM>> optional config file. This greatly shortens the command line. Try new SM>> version, please. NPC> I was already thinking in the same direction for a future update! ;-) Is it works now? Have nice nights. Stas Mishchenkov. --- Мудрость - это когда ты всё понимаешь, но уже не огорчаешься. * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858) .