Hi Janis,
A week ago I send you this crashmail:
"""
Are you sending the right Z1 nodelist segment for the weekly nodelist to Ward?
I'm seeing entries that don't seem correct for months now (compared to--- GEcho/32 & IM 2.50
the Z2 daily, and the Z1 weekly), for instance Bob Seaborn's net
entries:
Region,17,North_West,AB_AK_BC_ID_MB_MT_OR_NWT_SK_WA_YT,Bob_Seaborn,- Unpublished-,300,CM,MN,XX,MO,IBN:nwstar.dynu.net
Host,140,Prairie_Net,Saskatchewan_Canada,Bob_Seaborn,-Unpublished-,300, CM,MO,MN,XX,IBN:nwstar.tzo.com ,1,nwstar.tzo.com,Saskatchewan,Bob_Seaborn,-Unpublished-,300,CM,MN,XX, MO,IBN:nwstar.tzo.com,UNEC
The latter two have a host name that doesn't resolve and is different in
the Z1 weekly.
"""
This is still the case in this weeks Z2 nodelist...
Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)
Are you sending the right Z1 nodelist segment for the weekly nodelist
to Ward?
Then ward is not doing his job (as usual), my domain changed quite some time ago, and was properly updated by zc1 in our nodelist. Perhaps you should tell zc2 to "get with it!"
Then ward is not doing his job (as usual), my domain changed quite some time ago, and was properly updated by zc1 in our nodelist. Perhaps you should tell zc2 to "get with it!"
Then ward is not doing his job (as usual), my domain changed quite some time ago, and was properly updated by zc1 in our nodelist. Perhaps you should tell zc2 to "get with it!"
Hi Bob,
On 2017-11-10 09:50:00, you wrote to me:
Are you sending the right Z1 nodelist segment for the weekly nodelist
to Ward?
Then ward is not doing his job (as usual), my domain changed quite some
time ago, and was properly updated by zc1 in our nodelist. Perhaps you
should tell zc2 to "get with it!"
He said this is what he gets send from Janis for the weekly nodelist...
Hello Bob!
10 Nov 17 09:50, you wrote to Wilfred van Velzen:
Then ward is not doing his job (as usual), my domain changed quite some
time ago, and was properly updated by zc1 in our nodelist. Perhaps you
should tell zc2 to "get with it!"
Similar patterns can be found in the daily nodelists as well as the
Zone1
updates as published daily by ZC1.
So it would be nice if you addressed your praise, where praise is due.
Bob,
Then ward is not doing his job (as usual), my domain changed quitesomeBS> time ago, and was properly updated by zc1 in our nodelist.
Perhaps you
should tell zc2 to "get with it!"
If you only wouldn't mistake your mouth for an asshole and for once use braincells before talking...
Based on what I've read, you owe your denziens a major apology.
Praise: ZC1 is doing her job.
Non-praise: ZC2 apparently is not
Thre, happy now?
Then ward is not doing his job (as usual), my domain changed quite some
time ago, and was properly updated by zc1 in our nodelist. Perhaps you
should tell zc2 to "get with it!"
Similar patterns can be found in the daily nodelists as well as the
Zone1
updates as published daily by ZC1.
So it would be nice if you addressed your praise, where praise is due.
Praise: ZC1 is doing her job.
Non-praise: ZC2 apparently is not
If I search the zone2 dailylists for 'nwstar.tzo.com' sometimes it is there, sometimes it is not:
someAre you sending the right Z1 nodelist segment for the weekly nodelist
to Ward?
Then ward is not doing his job (as usual), my domain changed quite
time ago, and was properly updated by zc1 in our nodelist. Perhapsyou
should tell zc2 to "get with it!"
He said this is what he gets send from Janis for the weekly nodelist...
Then either he is screwing up, or (again) stating mistruths.
ZC1 has either more that one set of region-files to produce the zone1-file from or a flawed system. Your IBN-information in these zone1-files fluctuates from day to day, that's not my doing ... it's in the received files.
So it would be nice if you addressed your praise, where praise is due.Praise: ZC1 is doing her job.
Non-praise: ZC2 apparently is not
The config file where regions are included has lines like:
Region 17 region17.* 1:17/0
or
Region 17 region17 1:17/0
Bob,
Based on what I've read, you owe your denziens a major apology.
You are unable to conduct a well-argumented discussion.
ZC1 has either more that one set of region-files to produce the zone1---- GEcho/32 & IM 2.50
file from or a flawed system. Your IBN-information in these zone1-files fluctuates from day to day, that's not my doing ... it's in the received files.
ZC3 and ZC4 can see it also should they care, and Kees Van Eeten @ 2:280/5003 sees it too as he also receives the files.
You're denying the undeniable simply because you have no clue what
you're talking about and need a stick.
Pfftttt ....
\%/@rd
--- D'Bridge 3.99
* Origin: I will always keep a PC running WinXP (2:292/854)
Hi Bob.
10 Nov 17 18:48:00, you wrote to Kees van Eeten:
someThen ward is not doing his job (as usual), my domain changed quite
youtime ago, and was properly updated by zc1 in our nodelist. Perhaps
should tell zc2 to "get with it!"
Similar patterns can be found in the daily nodelists as well as the
Zone1
updates as published daily by ZC1.
So it would be nice if you addressed your praise, where praise is due.
Praise: ZC1 is doing her job.
Non-praise: ZC2 apparently is not
I receive the zone1 nodelist file echo from 1:154/10 and I store the
files for 30 days. All weekly nodelists from day 286 to day 314 contain
the nwstar.dynu.net address for your 3 nodes. No problem there.
If I search the zone2 dailylists for 'nwstar.tzo.com' sometimes it is
there, sometimes it is not:
---------- DAILYLST.302--- GEcho/32 & IM 2.50
---------- DAILYLST.303
---------- DAILYLST.304
---------- DAILYLST.305 Region,17,North_West,AB_AK_BC_ID_MB_MT_OR_NWT_SK_WA_YT,Bob_Seaborn,-Un published-,300,CM,MN,XX,MO,IBN:nwstar.tzo.com Host,140,Prairie_Net,Saskatchewan_Canada,Bob_Seaborn,-Unpublished-,300 ,CM,MO,MN,XX,IBN:nwstar.tzo.com ,1,nwstar.tzo.com,Saskatchewan,Bob_Seaborn,-Unpublished-,300,CM,MN,XX, MO,IBN:nwstar.tzo.com,UNEC
---------- DAILYLST.306
---------- DAILYLST.307 Host,140,Prairie_Net,Saskatchewan_Canada,Bob_Seaborn,-Unpublished-,300 ,CM,MO,MN,XX,IBN:nwstar.tzo.com ,1,nwstar.tzo.com,Saskatchewan,Bob_Seaborn,-Unpublished-,300,CM,MN,XX, MO,IBN:nwstar.tzo.com,UNEC
---------- DAILYLST.308
---------- DAILYLST.309
---------- DAILYLST.310
---------- DAILYLST.311
---------- DAILYLST.312 Region,17,North_West,AB_AK_BC_ID_MB_MT_OR_NWT_SK_WA_YT,Bob_Seaborn,-Un published-,300,CM,MN,XX,MO,IBN:nwstar.tzo.com Host,140,Prairie_Net,Saskatchewan_Canada,Bob_Seaborn,-Unpublished-,300 ,CM,MO,MN,XX,IBN:nwstar.tzo.com ,1,nwstar.tzo.com,Saskatchewan,Bob_Seaborn,-Unpublished-,300,CM,MN,XX, MO,IBN:nwstar.tzo.com,UNEC
---------- DAILYLST.313
---------- DAILYLST.314 Host,140,Prairie_Net,Saskatchewan_Canada,Bob_Seaborn,-Unpublished-,300 ,CM,MO,MN,XX,IBN:nwstar.tzo.com ,1,nwstar.tzo.com,Saskatchewan,Bob_Seaborn,-Unpublished-,300,CM,MN,XX, MO,IBN:nwstar.tzo.com,UNEC
---------- DAILYLST.315 Host,140,Prairie_Net,Saskatchewan_Canada,Bob_Seaborn,-Unpublished-,300 ,CM,MO,MN,XX,IBN:nwstar.tzo.com ,1,nwstar.tzo.com,Saskatchewan,Bob_Seaborn,-Unpublished-,300,CM,MN,XX, MO,IBN:nwstar.tzo.com,UNEC
And the question: WTF?
It would be nice if all *C's would release their own segments which are
used to create the actual nodelist. They contain no secrets.
'Tommi
---
* Origin: 2001:470:1f15:cb0:f1d0:2:221:6 (2:221/6)
Hi Bob,
On 2017-11-10 18:47:00, you wrote to me:
someAre you sending the right Z1 nodelist segment for the weekly nodelist
to Ward?
Then ward is not doing his job (as usual), my domain changed quite
time ago, and was properly updated by zc1 in our nodelist. Perhapsyou
should tell zc2 to "get with it!"
He said this is what he gets send from Janis for the weekly nodelist...
Then either he is screwing up, or (again) stating mistruths.
You are making a fool of yourself. Please read the messages that Ward
and others have sent in this thread carefully!
Bye, Wilfred.--- GEcho/32 & IM 2.50
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)
Hi Bob!
10 Nov 2017 18:48, from Bob Seaborn -> Kees van Eeten:
So it would be nice if you addressed your praise, where praise is due.Praise: ZC1 is doing her job.
Non-praise: ZC2 apparently is not
I would very much appreciate it if we would focus less on insulting
fellow participants, and more on solving the issue at hand!
Based on the evidence in this echo I do not see arguments supporting--- GEcho/32 & IM 2.50
your praise distribution.
Maybe Janis can comment here, and work towards SOLVING the issue?
CU, Ricsi
--- GoldED+/LNX
* Origin: Success has thousand fathers, but failure is an orphan. (2:310/31)
Hello Bob!
10 Nov 17 18:48, you wrote to me:
Praise: ZC1 is doing her job.
We are not questioning whether ZC1 is doing her job, only the
procedures she
uses for collating the Z1 segment of the nodelist are the issue.
--- GEcho/32 & IM 2.50Non-praise: ZC2 apparently is not
Apparently you have not checked the facts, but only express your
personal
feelings
Thre, happy now?
Not really.
For some statistical statistical use in the past, I installed a
procedure
to collect the daily nodelist from http://www.filegate.net/dailylist/
From the structure of the nodelist I assume it is generated by ZC1 as
Zone
order is 1 2 3 4. ZC2 nodelists order the zones 2 1 3 4.
The following abstract of your listing is found.
nodelist.255:Region,17,.....,IBN:nwstar.tzo.com nodelist.255:Host,140,......,IBN:nwstar.tzo.com nodelist.255:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.256:Region,17,.....,IBN:nwstar.tzo.com nodelist.256:Host,140,......,IBN:nwstar.tzo.com nodelist.256:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.257:Region,17,.....,IBN:nwstar.dynu.net nodelist.257:Host,140,......,IBN:nwstar.tzo.com nodelist.257:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.258:Region,17,.....,IBN:nwstar.dynu.net nodelist.258:Host,140,......,IBN:nwstar.dynu.net nodelist.258:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.259:Region,17,.....,IBN:nwstar.dynu.net nodelist.259:Host,140,......,IBN:nwstar.dynu.net nodelist.259:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.260:Region,17,.....,IBN:nwstar.dynu.net nodelist.260:Host,140,......,IBN:nwstar.dynu.net nodelist.260:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.261:Region,17,.....,IBN:nwstar.dynu.net nodelist.261:Host,140,......,IBN:nwstar.dynu.net nodelist.261:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.262:Region,17,.....,IBN:nwstar.tzo.com nodelist.262:Host,140,......,IBN:nwstar.tzo.com nodelist.262:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.263:Region,17,.....,IBN:nwstar.tzo.com nodelist.263:Host,140,......,IBN:nwstar.tzo.com nodelist.263:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.264:Region,17,.....,IBN:nwstar.dynu.net nodelist.264:Host,140,......,IBN:nwstar.tzo.com nodelist.264:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.265:Region,17,.....,IBN:nwstar.dynu.net nodelist.265:Host,140,......,IBN:nwstar.dynu.net nodelist.265:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.266:Region,17,.....,IBN:nwstar.dynu.net nodelist.266:Host,140,......,IBN:nwstar.dynu.net nodelist.266:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.267:Region,17,.....,IBN:nwstar.dynu.net nodelist.267:Host,140,......,IBN:nwstar.dynu.net nodelist.267:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.268:Region,17,.....,IBN:nwstar.dynu.net nodelist.268:Host,140,......,IBN:nwstar.dynu.net nodelist.268:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.269:Region,17,.....,IBN:nwstar.tzo.com nodelist.269:Host,140,......,IBN:nwstar.tzo.com nodelist.269:Host,140,......,IBN:nwstar.tzo.com nodelist.269:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.270:Region,17,.....,IBN:nwstar.tzo.com nodelist.270:Host,140,......,IBN:nwstar.tzo.com nodelist.270:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.271:Region,17,.....,IBN:nwstar.dynu.net nodelist.271:Host,140,......,IBN:nwstar.tzo.com nodelist.271:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.272:Region,17,.....,IBN:nwstar.dynu.net nodelist.272:Host,140,......,IBN:nwstar.dynu.net nodelist.272:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.273:Region,17,.....,IBN:nwstar.dynu.net nodelist.273:Host,140,......,IBN:nwstar.dynu.net nodelist.273:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.274:Region,17,.....,IBN:nwstar.dynu.net nodelist.274:Host,140,......,IBN:nwstar.dynu.net nodelist.274:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.275:Region,17,.....,IBN:nwstar.dynu.net nodelist.275:Host,140,......,IBN:nwstar.dynu.net nodelist.275:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.276:Region,17,.....,IBN:nwstar.tzo.com nodelist.276:Host,140,......,IBN:nwstar.tzo.com nodelist.276:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.277:Region,17,.....,IBN:nwstar.tzo.com nodelist.277:Host,140,......,IBN:nwstar.tzo.com nodelist.277:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.278:Region,17,.....,IBN:nwstar.dynu.net nodelist.278:Host,140,......,IBN:nwstar.tzo.com nodelist.278:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.279:Region,17,.....,IBN:nwstar.dynu.net nodelist.279:Host,140,......,IBN:nwstar.dynu.net nodelist.279:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.280:Region,17,.....,IBN:nwstar.dynu.net nodelist.280:Host,140,......,IBN:nwstar.dynu.net nodelist.280:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.281:Region,17,.....,IBN:nwstar.dynu.net nodelist.281:Host,140,......,IBN:nwstar.dynu.net nodelist.281:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.282:Region,17,.....,IBN:nwstar.dynu.net nodelist.282:Host,140,......,IBN:nwstar.dynu.net nodelist.282:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.283:Region,17,.....,IBN:nwstar.tzo.com nodelist.283:Host,140,......,IBN:nwstar.tzo.com nodelist.283:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.284:Region,17,.....,IBN:nwstar.tzo.com nodelist.284:Host,140,......,IBN:nwstar.tzo.com nodelist.284:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.285:Region,17,.....,IBN:nwstar.dynu.net nodelist.285:Host,140,......,IBN:nwstar.tzo.com nodelist.285:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.286:Region,17,.....,IBN:nwstar.dynu.net nodelist.286:Host,140,......,IBN:nwstar.dynu.net nodelist.286:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.287:Region,17,.....,IBN:nwstar.dynu.net nodelist.287:Host,140,......,IBN:nwstar.dynu.net nodelist.287:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.288:Region,17,.....,IBN:nwstar.dynu.net nodelist.288:Host,140,......,IBN:nwstar.dynu.net nodelist.288:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.289:Region,17,.....,IBN:nwstar.dynu.net nodelist.289:Host,140,......,IBN:nwstar.dynu.net nodelist.289:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.290:Region,17,.....,IBN:nwstar.tzo.com nodelist.290:Host,140,......,IBN:nwstar.tzo.com nodelist.290:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.291:Region,17,.....,IBN:nwstar.tzo.com nodelist.291:Host,140,......,IBN:nwstar.tzo.com nodelist.291:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.292:Region,17,.....,IBN:nwstar.dynu.net nodelist.292:Host,140,......,IBN:nwstar.tzo.com nodelist.292:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.293:Region,17,.....,IBN:nwstar.dynu.net nodelist.293:Host,140,......,IBN:nwstar.dynu.net nodelist.293:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.294:Region,17,.....,IBN:nwstar.dynu.net nodelist.294:Host,140,......,IBN:nwstar.dynu.net nodelist.294:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.295:Region,17,.....,IBN:nwstar.dynu.net nodelist.295:Host,140,......,IBN:nwstar.dynu.net nodelist.295:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.296:Region,17,.....,IBN:nwstar.dynu.net nodelist.296:Host,140,......,IBN:nwstar.dynu.net nodelist.296:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.297:Region,17,.....,IBN:nwstar.tzo.com nodelist.297:Host,140,......,IBN:nwstar.tzo.com nodelist.297:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.298:Region,17,.....,IBN:nwstar.tzo.com nodelist.298:Host,140,......,IBN:nwstar.tzo.com nodelist.298:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.299:Region,17,.....,IBN:nwstar.dynu.net nodelist.299:Host,140,......,IBN:nwstar.tzo.com nodelist.299:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.300:Region,17,.....,IBN:nwstar.dynu.net nodelist.300:Host,140,......,IBN:nwstar.dynu.net nodelist.300:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.301:Region,17,.....,IBN:nwstar.dynu.net nodelist.301:Host,140,......,IBN:nwstar.dynu.net nodelist.301:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.302:Region,17,.....,IBN:nwstar.dynu.net nodelist.302:Host,140,......,IBN:nwstar.dynu.net nodelist.302:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.303:Region,17,.....,IBN:nwstar.dynu.net nodelist.303:Host,140,......,IBN:nwstar.dynu.net nodelist.303:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.304:Region,17,.....,IBN:nwstar.tzo.com nodelist.304:Host,140,......,IBN:nwstar.tzo.com nodelist.304:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.305:Region,17,.....,IBN:nwstar.tzo.com nodelist.305:Host,140,......,IBN:nwstar.tzo.com nodelist.305:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.306:Region,17,.....,IBN:nwstar.dynu.net nodelist.306:Host,140,......,IBN:nwstar.tzo.com nodelist.306:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.307:Region,17,.....,IBN:nwstar.dynu.net nodelist.307:Host,140,......,IBN:nwstar.dynu.net nodelist.307:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.308:Region,17,.....,IBN:nwstar.dynu.net nodelist.308:Host,140,......,IBN:nwstar.dynu.net nodelist.308:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.309:Region,17,.....,IBN:nwstar.dynu.net nodelist.309:Host,140,......,IBN:nwstar.dynu.net nodelist.309:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.310:Region,17,.....,IBN:nwstar.dynu.net nodelist.310:Host,140,......,IBN:nwstar.dynu.net nodelist.310:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.311:Region,17,.....,IBN:nwstar.tzo.com nodelist.311:Host,140,......,IBN:nwstar.tzo.com nodelist.311:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.312:Region,17,.....,IBN:nwstar.tzo.com nodelist.312:Host,140,......,IBN:nwstar.tzo.com nodelist.312:,1,nwstar.tzo.com,.....,IBN:nwstar.tzo.com,UNEC nodelist.313:Region,17,.....,IBN:nwstar.dynu.net nodelist.313:Host,140,......,IBN:nwstar.tzo.com nodelist.314:Region,17,.....,IBN:nwstar.dynu.net nodelist.314:Host,140,......,IBN:nwstar.dynu.net nodelist.314:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC nodelist.315:Region,17,.....,IBN:nwstar.dynu.net nodelist.315:Host,140,......,IBN:nwstar.dynu.net nodelist.315:,1,nwstar.dynu.net,.....,IBN:nwstar.dynu.net,UNEC
Please be aware that there are other lines in the Z1 segment, that show
a
similar pattern.
Before you shoot from the hip again, it would be nice if you could
verify the
above facts first.
Thank,
Kees
--- GoldED+/LNX 1.1.5
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
The latter two have a host name that doesn't resolve and is different in the Z
The latter two have a host name that doesn't resolve and is different in the
Z
We were away for the weekend, but seeing the above I deleted the following segments from my processing directory:
region17.311 region17.312 region17.313
That should take care of the problem.
That should take care of the problem.
That should take care of the problem.
So it wasn't Ward that was at fault, like someone here claimed over
and over again?
We were away for the weekend, but seeing the above I deleted the
following segments from my processing directory:
region17.311 region17.312 region17.313
That should take care of the problem.
Lets wait for tomorrow. :)
On 2017-11-12 10:21:48, you wrote to Janis Kracht:
Lets wait for tomorrow. :)
Lets wait for the weekly... ;)
Lets wait for tomorrow. :)
Lets wait for the weekly... ;)
That also, but tomorrow first. ;-)
Hello Bob!
10 Nov 17 18:48, you wrote to me:
Praise: ZC1 is doing her job.
We are not questioning whether ZC1 is doing her job, only the
procedures she
uses for collating the Z1 segment of the nodelist are the issue.
That is something you should take up with ZC1, NOT me.
Hello Bob!
11 Nov 17 10:14, you wrote to me:
Hello Bob!
10 Nov 17 18:48, you wrote to me:
Praise: ZC1 is doing her job.
We are not questioning whether ZC1 is doing her job, only the
procedures she
uses for collating the Z1 segment of the nodelist are the issue.
That is something you should take up with ZC1, NOT me.
Why not it is about your entry in the nodelist that flip-flops between
correct en false notations in nodelist that are dependant on updates
sent bij ZC1 and moreover, you have her ear.
All I know for sure is that when I changed domains, I tested the proposed change for over a week, submitted my updates once to ZC1, and have had no need to do anything since. Every one of the subsequent z1 nodelists have been correct. If the same is not true in z2, then I'd suggest that you start with whoever issues the z2 nodelist, and, if necessary, work back from there. sorry, I make no use of the daily nodelists, so cannot say what goes on with them, if anything. Also I use the nodelist/diff as issued by ZC!, nobody else.
But definitely don't go blaming me!
Hello Bob!
12 Nov 17 14:15, you wrote to me:
All I know for sure is that when I changed domains, I tested theproposed
change for over a week, submitted my updates once to ZC1, and have hadno
need to do anything since. Every one of the subsequent z1 nodelistshave
been correct. If the same is not true in z2, then I'd suggest that you
start with whoever issues the z2 nodelist, and, if necessary, work back
from there. sorry, I make no use of the daily nodelists, so cannot say
what goes on with them, if anything. Also I use the nodelist/diff as
issued by ZC!, nobody else.
I think the issue has been solved, at least where your nodelist entries
are
involved. Unfortunately the reported solution does not solve similar
issues
found in other region files. At least ZC1 is now aware that there are
issues at large. Some of will keep pushing till all is sound.
But definitely don't go blaming me!
I do not think that I blamed you for anything. I only reacted to the
fact that
personal feeling caused you to quickly point to sure causes, of what
was
going on.
It would be nice if this Ping-Pong game between you and Ward would come
to an end. It does more harm then good to Fidonet.
Do we not have the ability to say and
realize that "OK, Shit Happened. Lets fix it and move on"?
It would be nice if this Ping-Pong game between you and Ward wouldConsidering that ward has proven to myself, and others over here that
come to an end. It does more harm then good to Fidonet.
he is a liar, and cannot be trusted, plus he loves to blame problems
on me, despite the fact that I have nothing to do with them, I
honestly doubt that it will be settled very soon, however our concerns have been noted.
It has become apparent that some mistakes or errors were made in one
or more nodelist entries. It amazes me how much effort and time can be expended in the placing of blame and alleged responsibility for what happened. And so little apparent time in fixing and correcting the the error. We are all capable of making mistakes and errors. We have all
done it before and are destined to do it again at some point in the future. Do we not have the ability to say and realize that "OK, Shit Happened. Lets fix it and move on"?
The latter two have a host name that doesn't resolve and is different in the
Z
We were away for the weekend, but seeing the above I deleted the following segments from my processing directory:
region17.311 region17.312 region17.313
That should take care of the problem.
That should take care of the problem.
That should take care of the problem.
So it wasn't Ward that was at fault, like someone here claimed over
and over again?
We were away for the weekend, but seeing the above I deleted the
following segments from my processing directory:
region17.311 region17.312 region17.313
That should take care of the problem.
Lets wait for tomorrow. :)
I honestly doubt that it will be settled very soon, however
our concerns have been noted.
The latter two have a host name that doesn't resolve and is different
in the Z
We were away for the weekend, but seeing the above I deleted the following segments from my processing directory:
region17.311 region17.312 region17.313
That should take care of the problem.
,20,The_North_American_Backbone,Zone_1,NAB,-Unpublished-,300,CM,MO,XX,INA :the-estar.com,IBN4c4
,120,RemoteAccess_Help_USA,Central_NC_USA,mark_lewis,1-919-774-5930,33600 ,TEW,ICM,XA,V32b,V42b,H16,V32t,V34,IBN:wpusa.dynip.com,ITN,IVM,IFT82,83c82,83
Down,545,Rocasa_FTNGate,Lansing_MI,RJ_Clay,-Unpublished-,300,XA,CM,INA:ft n.rocasa.us,IBN,IFC,ITN:60177,PING,U,IPv6 ,546,Rocasa_BBBS,Lansing_MI,Robert_Clay,000-192-210-236-220,300,XX,CM,INA :bbbs.rocasa.biz,IBN,IUC:filebot@rocasa.biz148c148
Host,229,West_ON/Toronto/GTA,Toronto_ON,Nick_Andre,1-647-847-2083,9600,CM ,XX,INA:bbs.darkrealms.ca,IBN,ICM161c161
Host,249,East_ON/PQ/NB/PE/NS/NF,Montreal_Quebec,Luc_Mccarragher,-Unpublis hed-,300,CM,IBN:mccarragher.org246,247c246,247
Hub,300,RVA_Fido_Support,Richmond_VA,Ozz_Nixon,-Unpublished-,300,CM,XX,IN A:exchangebbs.com,IBN,ITN,IFT ,362,RVA_Fido_Support,Richmond_VA,Ozz_Nixon,-Unpublished-,300,CM,XX,INA:e xchangebbs.com,IBN,ITN,IFT249,250c249,250
Region,14,Mid_West,IA_KS_MN_MO_NE_ND_SD,Jeff_Smith,-Unpublished-,300,CM,X X,ITN,INA:bbs.ouijabrd.net,IBN ,5,Region_14_IP_Server,Anoka_MN,Jeff_Smith,-Unpublished-,300,CM,XX,ITN,IF T,INA:bbs.ouijabrd.net,IBN253,254c253,254
Host,282,MidWest,IA.KS.MN.MO.NE.ND.SD,Will_Du_Chene,-Unpublished-,300,CM, INA:crystalp.duckdns.org,ITN,IFT,IBN,IFC ,1031,The_Ouija_Board,Anoka_MN,Jeff_Smith,-Unpublished-,300,CM,XX,ITN,INA :bbs.ouijabrd.net,IBN260a261
,1059,Temple_Of_Syrinx,St_Paul_MN,Daniel_Kidd,-Unpublished-,300,CM,XX,IBN ,ITN,,INA:templeofsyrinx.info263c264,273
Host,288,The_Curmudgeons_Place,Castlewood_SD,Gaylen_Hintz,-Unpublished-,3 00,CM,IBN:curmudge.hopto.org ,34,The_Curmudgeons_Place,Castlewood_SD,Gaylen_Hintz,-Unpublished-,300,CM ,IBN:curmudge.hopto.org ,35,The_Curmudgeons_Place,Castlewood_SD,Gaylen_Hintz,-Unpublished-,300,CM ,MO,IBN,INA:curmudge.hopto.org ,9999,New_Fidonet_Node,Anywhere_MN,New_Fido_SysOp,-Unpublished-,9600267c277
;
Host,298,Raiders_Inc_BBS,Wichita_Kansas,Jon_Justvig,-Unpublished-,300,CM, INA:vintagebbsing.com,ITN,IBN ,25,Raiders_Inc_BBS,Wichita_Kansas,Jon_Justvig,-Unpublished-,300,CM,INA:v intagebbsing.com,ITN,IBN ,9999,New_Fidonet_Node,Anywhere_KS,New_Fido_SysOp,-Unpublished-,300
;
Host,299,Nebraska_Net,Nebraska_USA,Jeff_Smith,-Unpublished-,300,CM,XX,IFC ,IFT,INA:bbs.ouijabrd.net,IBN
Host,300,Iowa_Net,Iowa_USA,Jeff_Smith,-Unpublished-,300,CM,XX,IFC,IFT,INA :bbs.ouijabrd.net,IBN272,274c282,284
Region,15,Mountain_States,AZ_CO_NM_UT_WY,Tj_Barlow,-Unpublished-,9600,ICM ,IBN,IFT,IFC,ITN:60177,INA:region15.net:24554 ,1,Region15_Echomail_Coordinator,Colorado_Springs_CO,Terry_Barlow,1-801-2 50-2424,9600,CM,XX,IBN,ITN,INA:region15.net:24554 ,2,Regional_Coordinator,Colorado_Springs_CO,Terry_Barlow,-Unpublished-,96 00,ICM,IBN,IFT,IFC,ITN:60177,INA:region15.net:24554299a310
,706,RPG_Circus_BBS,Mesa_AZ,Jeffrey_Brissette,-Unpublished-,9600,CM,XX,H1 6,V32b,V42b,V34,V32t,X2C,INA:162.208.11.127,IBN410c421
Region,18,SE_US_&_Caribbean_(2017/320),AL_FL_GA_MS_NC_SC_TN_PR,mark_lewis ,1-919-774-5930,33600,XA,V34,CM,ITN,INA:ftn.wpusa.dynip.com,IBN,IVM,PING477c488
Host,3634,North_Carolina_USA_(2017/320),central_NC_USA,mark_lewis,1-919-7 74-5930,33600,XA,V34,CM,ITN,INA:ftn.wpusa.dynip.com,IBN,IVM,PING522a534
,5016,End_Of_The_Line_BBS,Plano_Tx,Nigel_Reed,-Unpublished-,300,CM,XA,INA :ipv4.endofthelinebbs.com:2300,IBN:ipv4.endofthelinebbs.com:24554546d557
Lets wait for tomorrow. :)
Lets wait for the weekly... ;)
That also, but tomorrow first. ;-)
Lets wait for tomorrow. :)
Lets wait for the weekly... ;)
That also, but tomorrow first. ;-)
Regarding the weekly, Janis will have to redo her homework! :-(
It would be best to start using just one nodelist, and release it
daily. IMHO.
The latter two have a host name that doesn't resolve and is different
in the Z
We were away for the weekend, but seeing the above I deleted the
following segments from my processing directory:
region17.311 region17.312 region17.313
That should take care of the problem.
That only fixed the entries for region 17. There are still lots of other differences between the Z1 segements in the Z1 and Z2 weekly. Here's the diff output for .321.
=== Begin diff.out ===-+
2c2
< ,20,The_North_American_Backbone,Zone_1,NAB,-Unpublished-,300,CM,MO,XX,INA
:cmech.dynip.com,IBN -+-
,20,The_North_American_Backbone,Zone_1,NAB,-Unpublished-,300,CM,MO,XX,INA4c4
:the-estar.com,IBN
< ,120,RemoteAccess_Help_USA,Central_NC_USA,mark_lewis,1-919-774-5930,33600
,XA,V34,CM,ITN,INA:ftn.wpusa.dynip.com,IBN,IVM,PING -+-
,120,RemoteAccess_Help_USA,Central_NC_USA,mark_lewis,1-919-774-5930,3360082,83c82,83
,TEW,ICM,XA,V32b,V42b,H16,V32t,V34,IBN:wpusa.dynip.com,ITN,IVM,IFT
< ,545,Rocasa_FTN_Testing,Lansing_MI,RJ_Clay,000-198-37-102-11,300,XA,CM,IN
A:ftn.rocasa.com,IBN:24555,IFC,ITN:60177,PING,U,IPv6 < Down,546,Rocasa_BBBS,Lansing_MI,Robert_Clay,-Unpublished-,300,XX,CM,INA:bbb
s.rocasa.biz,IBN,IUC:filebot@rocasa.biz -+-
Down,545,Rocasa_FTNGate,Lansing_MI,RJ_Clay,-Unpublished-,300,XA,CM,INA:ft148c148
n.rocasa.us,IBN,IFC,ITN:60177,PING,U,IPv6
,546,Rocasa_BBBS,Lansing_MI,Robert_Clay,000-192-210-236-220,300,XX,CM,INA
:bbbs.rocasa.biz,IBN,IUC:filebot@rocasa.biz
< Host,229,Greater_Toronto_Area,Toronto_ON,Nick_Andre,1-647-847-2083,9600,C
M,XX,INA:bbs.darkrealms.ca,IBN,ICM -+-
Host,229,West_ON/Toronto/GTA,Toronto_ON,Nick_Andre,1-647-847-2083,9600,CM161c161
,XX,INA:bbs.darkrealms.ca,IBN,ICM
< Host,249,Lake_Ontario_Net_(Interim_NC),Toronto_ON,Nick_Andre,1-647-847-20
83,9600,CM,XX,INA:bbs.darkrealms.ca,IBN,ICM -+-
Host,249,East_ON/PQ/NB/PE/NS/NF,Montreal_Quebec,Luc_Mccarragher,-Unpublis246,247c246,247
hed-,300,CM,IBN:mccarragher.org
< Hub,300,RVA_Fido_Support,Richmond_VA,Ozz_Nixon,-Unpublished-,300,CM,XX,IN
A:fido.pwnz.org,IBN,ITN,IFT < ,362,RVA_Fido_Support,Richmond_VA,Ozz_Nixon,-Unpublished-,300,CM,XX,INA:fid
o.pwnz.org,IBN,ITN,IFT -+-
Hub,300,RVA_Fido_Support,Richmond_VA,Ozz_Nixon,-Unpublished-,300,CM,XX,IN249,250c249,250
A:exchangebbs.com,IBN,ITN,IFT
,362,RVA_Fido_Support,Richmond_VA,Ozz_Nixon,-Unpublished-,300,CM,XX,INA:e
xchangebbs.com,IBN,ITN,IFT
< Region,14,Mid_West,IA_KS_MN_MO_NE_ND_SD,Jeff_Smith,-Unpublished-,300,CM,M
O,ITN,IFT,INA:bbs.ouijabrd.net,IBN < ,5,Region_14_IP_Server,Anoka_MN,Jeff_Smith,-Unpublished-,300,CM,MO,ITN,IFT,
INA:bbs.ouijabrd.net,IBN -+-
Region,14,Mid_West,IA_KS_MN_MO_NE_ND_SD,Jeff_Smith,-Unpublished-,300,CM,X253,254c253,254
X,ITN,INA:bbs.ouijabrd.net,IBN
,5,Region_14_IP_Server,Anoka_MN,Jeff_Smith,-Unpublished-,300,CM,XX,ITN,IF
T,INA:bbs.ouijabrd.net,IBN
< Host,282,Mid_West,IA.KS.MN.MO.NE.ND.SD,Will_Du_Chene,-Unpublished-,300,CM
,INA:crystalp.duckdns.org,ITN,IFT,IBN,IFC < ,1031,The_Ouija_Board,Anoka_MN,Jeff_Smith,-Unpublished-,300,CM,ITN,INA:bbs.
ouijabrd.net,IBN -+-
Host,282,MidWest,IA.KS.MN.MO.NE.ND.SD,Will_Du_Chene,-Unpublished-,300,CM,260a261
INA:crystalp.duckdns.org,ITN,IFT,IBN,IFC
,1031,The_Ouija_Board,Anoka_MN,Jeff_Smith,-Unpublished-,300,CM,XX,ITN,INA
:bbs.ouijabrd.net,IBN
,1059,Temple_Of_Syrinx,St_Paul_MN,Daniel_Kidd,-Unpublished-,300,CM,XX,IBN263c264,273
,ITN,,INA:templeofsyrinx.info
< Host,299,Nebraska_Net,Nebraska_USA,Jeff_Smith,-Unpublished-,300,CM,MO,IFC
,IFT,INA:bbs.ouijabrd.net,IBN -+-
Host,288,The_Curmudgeons_Place,Castlewood_SD,Gaylen_Hintz,-Unpublished-,3267c277
00,CM,IBN:curmudge.hopto.org
,34,The_Curmudgeons_Place,Castlewood_SD,Gaylen_Hintz,-Unpublished-,300,CM
,IBN:curmudge.hopto.org
,35,The_Curmudgeons_Place,Castlewood_SD,Gaylen_Hintz,-Unpublished-,300,CM
,MO,IBN,INA:curmudge.hopto.org
,9999,New_Fidonet_Node,Anywhere_MN,New_Fido_SysOp,-Unpublished-,9600
;
Host,298,Raiders_Inc_BBS,Wichita_Kansas,Jon_Justvig,-Unpublished-,300,CM,
INA:vintagebbsing.com,ITN,IBN
,25,Raiders_Inc_BBS,Wichita_Kansas,Jon_Justvig,-Unpublished-,300,CM,INA:v
intagebbsing.com,ITN,IBN
,9999,New_Fidonet_Node,Anywhere_KS,New_Fido_SysOp,-Unpublished-,300
;
Host,299,Nebraska_Net,Nebraska_USA,Jeff_Smith,-Unpublished-,300,CM,XX,IFC
,IFT,INA:bbs.ouijabrd.net,IBN
< Host,300,Iowa_Net,Iowa_USA,Jeff_Smith,-Unpublished-,300,CM,MO,IFC,IFT,INA
:bbs.ouijabrd.net,IBN -+-
Host,300,Iowa_Net,Iowa_USA,Jeff_Smith,-Unpublished-,300,CM,XX,IFC,IFT,INA272,274c282,284
:bbs.ouijabrd.net,IBN
< Region,15,Mountain_States,AZ_CO_NM_UT_WY,Tj_Barlow,-Unpublished-,9600,CM,
XX,H16,V32b,V42b,V34,V32t,X2C,INA:region15.net,IBN:24554,IFT,ITN < ,1,Region15_Echomail_Coordinator,Colorado_Springs_CO,Terry_Barlow,-Unpublis
hed-,9600,CM,XX,H16,V32b,V42b,V34,V32t,X2C,INA:region15.net,IBN:24554,IFT,I
TN < ,2,Regional_Coordinator,Colorado_Springs_CO,Terry_Barlow,-Unpublished-,9600
,CM,XX,H16,V32b,V42b,V34,V32t,X2C,INA:region15.net,IBN:24554,IFT,ITN -+-
Region,15,Mountain_States,AZ_CO_NM_UT_WY,Tj_Barlow,-Unpublished-,9600,ICM299a310
,IBN,IFT,IFC,ITN:60177,INA:region15.net:24554
,1,Region15_Echomail_Coordinator,Colorado_Springs_CO,Terry_Barlow,1-801-2
50-2424,9600,CM,XX,IBN,ITN,INA:region15.net:24554
,2,Regional_Coordinator,Colorado_Springs_CO,Terry_Barlow,-Unpublished-,96
00,ICM,IBN,IFT,IFC,ITN:60177,INA:region15.net:24554
,706,RPG_Circus_BBS,Mesa_AZ,Jeffrey_Brissette,-Unpublished-,9600,CM,XX,H1410c421
6,V32b,V42b,V34,V32t,X2C,INA:162.208.11.127,IBN
< Region,18,SE_US_&_Caribbean_(2017/319),AL_FL_GA_MS_NC_SC_TN_PR,mark_lewis
,1-919-774-5930,33600,XA,V34,CM,ITN,INA:ftn.wpusa.dynip.com,IBN,IVM,PING
-
Region,18,SE_US_&_Caribbean_(2017/320),AL_FL_GA_MS_NC_SC_TN_PR,mark_lewis477c488
,1-919-774-5930,33600,XA,V34,CM,ITN,INA:ftn.wpusa.dynip.com,IBN,IVM,PING
< Host,3634,North_Carolina_USA_(2017/319),central_NC_USA,mark_lewis,1-919-7
74-5930,33600,XA,V34,CM,ITN,INA:ftn.wpusa.dynip.com,IBN,IVM,PING -+-
Host,3634,North_Carolina_USA_(2017/320),central_NC_USA,mark_lewis,1-919-7522a534
74-5930,33600,XA,V34,CM,ITN,INA:ftn.wpusa.dynip.com,IBN,IVM,PING
,5016,End_Of_The_Line_BBS,Plano_Tx,Nigel_Reed,-Unpublished-,300,CM,XA,INA546d557
:ipv4.endofthelinebbs.com:2300,IBN:ipv4.endofthelinebbs.com:24554
< ,75,Positronium_Mystic_Pi,Lafayette_LA,Ben_Ritchey,-Unpublished-,300,CM,X
X,INA:cmech.dynip.com,IBN:24557,IFT:2121,ITN:2323
=== End diff.out ===
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)
It would be best to start using just one nodelist, and release it
daily. IMHO.
That would still depend on the segments send in by the lower C's.
,20,The_North_American_Backbone,Zone_1,NAB,-Unpublished-,300,CM,MO,XX,INA >>> :the-estar.com,IBN
,20,The_North_American_Backbone,Zone_1,NAB,-Unpublished-,300,CM,MO,XX
,I NA :the-estar.com,IBN
In the segment I sent Ward last night (zone1.328) the entry for "the-estar.com" is _not_ present.
THIS is the line in Zone1.328 delivered to Ward last night: ,20,The_North_American_Backbone,Zone_1,NAB,-Unpublished-,300,CM,MO,XX,INA:c
mech .dynip.com,IBN
Nor is it in the last nodelist I sent out in the DAILYLIST file echo, NOR is it in last night's nodelist.
This is the entry in all of those files I mention above: ,20,The_North_American_Backbone,Zone_1,NAB,-Unpublished-,300,CM,MO,X X,INA:cmech .dynip.com,IBN
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,041 |
Nodes: | 15 (0 / 15) |
Uptime: | 119:09:25 |
Calls: | 500,254 |
Calls today: | 2 |
Files: | 95,199 |
D/L today: |
338 files (45,084K bytes) |
Messages: | 464,339 |