Would someone have time to run their eye across the nodelist and create a text file that contains the countries we have represented in the fsxNet nodelist?
Ideally totals of how many nodes in each country would be great too.
Would someone have time to run their eye across the nodelist and create a text file that contains the countries we have represented in the fsxNet nodelist?
Result:
1 TWN
1 SVK
1 SGP
1 ROU
1 PHL
1 GRC
1 FRA
1 FIN
1 CZE
1 CRI
1 AUT
Would someone have time to run their eye across the nodelist and create a text file that contains the countries we have represented in the fsxNet nodelist?never
Ideally totals of how many nodes in each country would be great too.
It's been on my TO-DO to include such a thing in the nodelist but I have
got around to it.someone(s)
I also had plans to do a similar thing for HAM radio operators but never did that too.
Anywhoo just putting it out there to the wider community to see if
might like to compile such a thing for inclusion in the infopack?beautiful
My thanks in advance... if you do, just be sure to let folks know you are else we'll end up with three versions which I am sure will all be a
thing :)
--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
Would someone have time to run their eye across the nodelist and create a text file that contains the countries we have represented in the fsxNet nodelist?never
Ideally totals of how many nodes in each country would be great too.
It's been on my TO-DO to include such a thing in the nodelist but I have
got around to it.someone(s)
I also had plans to do a similar thing for HAM radio operators but never did that too.
Anywhoo just putting it out there to the wider community to see if
might like to compile such a thing for inclusion in the infopack?beautiful
My thanks in advance... if you do, just be sure to let folks know you are else we'll end up with three versions which I am sure will all be a
thing :)
--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
ARG - Argentina
AUS - Australia
AUT - Austria
BRA - Brazil
129 USA
25 CAN
19 AUS
8 NZL
6 GBR
5 SWE
5 GER
4 ARG
3 BRA
2 NLD
2 ITA
1 TWN
1 SVK
1 SGP
1 ROU
1 PHL
1 GRC
1 FRA
1 FIN
1 CRI
1 AUT
This may include some nodes that are listed multiple times. I've exluced Zone, Region, Host, Pvt, and Down nodes.
I wonder how best to automate things such that Zone, Region and Host are excluded along with Down but the rest are counted?
I wonder how best to automate things such that Zone, Region and Host are excluded along with Down but the rest are counted?
139 USA 25 CAN 20 AUS 10 NZL 7 SWE 7 GBR 6 GER 4 ARG 3 NLD 3 BRA 2
20 AUS
On 24 Feb 2020 at 08:53p, Avon pondered and said...
I wonder how best to automate things such that Zone, Region and Host excluded along with Down but the rest are counted?
Here ya' go:
: fat-dragon; sh scr FSXNET.059
139 United States
25 Canada
20 Australia
10 New Zealand
This should do it -- it includes entries starting with nothing/Pvt/Hold but no others:
Hello Avon!
On 24 Feb 2020, Avon said the following...
I wonder how best to automate things such that Zone, Region and Host are
excluded along with Down but the rest are counted?
This should do it -- it includes entries starting with
nothing/Pvt/Hold but
no others:
cat FSXNET.059 | \
grep -E '^(Pvt|Hold)?,' | \
sed -E 's/^[^,]*,[^,]+,[^,]+,[^,]+_([^,]+),.*/\1/'
grep -v AnyCountry | sort | uniq -c | sort -n -r
139 USA
25 CAN
20 AUS
10 NZL
7 SWE
7 GBR
6 GER
4 ARG
3 NLD
3 BRA
2 ITA
2 ESP
1 TWN
1 SVK
1 SGP
1 ROU
1 PHL
1 GRC
1 FRA
1 FIN
1 CZE
1 CRI
1 AUT
Best regards
Zip
Thanks for this. I thought the New Zealand figure might be to high, but then I realized I left in HUBs and now wonder if they should be excluded or not. Given they are stand alone systems that are running I guess they should stay in. What does everyone else think?
On 02-25-20 21:10, Avon wrote to tenser <=-
Thanks for this. I thought the New Zealand figure might be to high, but then I realized I left in HUBs and now wonder if they should be
excluded or not. Given they are stand alone systems that are running I guess they should stay in. What does everyone else think?
sorry about this,I now I have done this the wrong way, but will keep on working on it and I will be back.
Depends. If a system has a unique host:port and meets all other
criteria, it should be included, otherwise not. For example, :1/0 and :1/1 are often duplicate entries, depending on how the nodelist is structured.
Nothing to apologise for. I appreciate the update and will support you where I can :) Don't stress over the time it might take you to sort
your problems. It's a hobby and stuff doesn't need to happen overnight
:)
Sending good vibes your way.
Depends. If a system has a unique host:port and meets all other
criteria, it should be included, otherwise not. For example, :1/0 and :1/1 are often duplicate entries, depending on how the nodelist is structured.
On 02-26-20 12:21, Avon wrote to Vk3jed <=-
On 26 Feb 2020 at 09:01a, Vk3jed pondered and said...
Depends. If a system has a unique host:port and meets all other
criteria, it should be included, otherwise not. For example, :1/0 and :1/1 are often duplicate entries, depending on how the nodelist is structured.
Yep, thanks, good thoughts.
On 02-25-20 19:07, Netsurge wrote to Vk3jed <=-
The old *:*/1 structure is a hold over from when there were ZECs, RECs
and NECs (* echomail coordinator). This made sense in the dialup days
so that mail could flow between Zones/Regions/Nets at an affordable
cost, today, no need.
Yep, thanks, good thoughts.
I'm sure you'll get there. ;)
On 02-26-20 20:20, Avon wrote to Vk3jed <=-
On 26 Feb 2020 at 11:26a, Vk3jed pondered and said...
Yep, thanks, good thoughts.
I'm sure you'll get there. ;)
when we do will you let me know please :)
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 31 |
Nodes: | 8 (0 / 8) |
Uptime: | 191:09:45 |
Calls: | 2,082 |
Calls today: | 5 |
Files: | 11,137 |
Messages: | 947,708 |