Forum: Vertrauen

Z1 weekly nodelist segment in Z2 nodelist

From Wilfred van Velzen@2:280/464 to Janis Kracht on Fri Nov 10 13:51:43 2017

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 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)

From Bob Seaborn@1:140/12 to Wilfred van Velzen on Fri Nov 10 09:50:00 2017

Hi Janis,

A week ago I send you this crashmail:

"""
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!"

I'm seeing entries that don't seem correct for months now (compared to
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)

--- GEcho/32 & IM 2.50
* Origin: http://www.fidonet.ca (1:140/12)

From Wilfred van Velzen@2:280/464 to Bob Seaborn on Fri Nov 10 17:02:21 2017

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...

Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

From Kees van Eeten@2:280/5003.4 to Bob Seaborn on Fri Nov 10 17:14:02 2017

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.

Kees
--- GoldED+/LNX 1.1.5
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

From Ward Dossche@2:292/854 to Bob Seaborn on Sat Nov 11 00:57:41 2017

Bob,

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!"

If you only wouldn't mistake your mouth for an asshole and for once use braincells before talking...

It may be fun taking a swipe at me and my system, but you have nothing to go on. To assist in shutting up that hole in your head (copied from "Titanic") here's some factual information.

ZC1 produced ZONE1.312 file on Nov.8 03:04am CET and distributed it
ZC1 produced ZONE1.314 file on Nov.8 05:45am CET and distributed it
ZC1 produced ZONE1.313 file on Nov.9 03:05am CET and distributed it

These were sent within 4-5 minutes to the other ZCs. Now I will try to explain this to you simple so you will hopefully understand:

ZONE1.312 contains
******************
Region,17,...IBN:nwstar.tzo.com
Host,140,...IBN:nwstar.tzo.com
,1,nwstar.tzo.com...IBN:nwstar.tzo.com,UNEC

This information is 2 hours later overwritten by ZONE1.314

ZONE1.314 contains
******************
Region,17 ...IBN:nwstar.dynu.net
Host,140...IBN:nwstar.dynu.net
,1,nwstar.dynu.net...IBN:nwstar.dynu.net,UNEC

This information is 22 hours later overwritten by ZONE1.313

ZONE1.313 contains
******************
Region,17...IBN:nwstar.dynu.net
Host,140...IBN:nwstar.tzo.com
,1,nwstar.tzo.com...IBN:nwstar.tzo.com,UNEC

The next 44 hours no ZONE1-file is received.

What does it mean?

That on Nov.9th the ZONE1.314 file is used for DAILYLST-production.

That on Nov.10th the ZONE1.313 file is used for both DAILYLST- and NODELIST-production.

As a result there are serious discrepancies caused by a very erratic production
of ZONE1-files which seem to be produced in 2 different sets: one for the Friday world-nodelist and a totally different one for the daily lists.

It gets worse ... your ZC obviously is using differing multiple sets of region files during ZONE1-production.

So what she sends around on Wednesday (314) overwriting 312 and to be used on Friday, will be used on Thursday in the daily but overwritten later that day by
313 which will be used on Friday with different R17 information.

None of that is any of my doing, I compile what I get. We have a shadow nodelist-system in Z2 for bqck-up and verification running different software and it notices exactly the same things.

Wilfred Van Velzen has highlighted the issue by netmail without any result.

So for all subsequent whining, please address yourself to Janis and ask her how
on Earth she manages to mess-up the R17-information so badly between different ZONE1-files.

There are more remarks to be made about how the ZONE1-list is produced.

You may not be bothered by this, but everyone in Fidonet outside Zone-1 is.

For your further information, here-under relevant complete entries
from ZONE1-files which were received by all the other ZCs.

\%/@rd

***********************************************
ZONE1.312 -- Production date Nov.8 -- 03:04 CET ***********************************************

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.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 ====================================================================

***********************************************
ZONE1.313 -- Production date Nov.9 -- 03:05 CET *********************************************** 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 ====================================================================

***********************************************
ZONE1.314 -- Production date Nov.8 -- 05:45 CET *********************************************** 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.dynu.net ,1,nwstar.dynu.net,Saskatchewan,Bob_Seaborn,-Unpublished- ,300,CM,MN,XX,MO,IBN:nwstar.dynu.net,UNEC
--- D'Bridge 3.99
* Origin: I will always keep a PC running WinXP (2:292/854)

From Bob Seaborn@1:140/12 to Wilfred van Velzen on Fri Nov 10 18:47:00 2017

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...

Then either he is screwing up, or (again) stating mistruths.

.....Bob
--- GEcho/32 & IM 2.50
* Origin: http://www.fidonet.ca (1:140/12)

From Bob Seaborn@1:140/12 to Kees van Eeten on Fri Nov 10 18:48:01 2017

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.

Praise: ZC1 is doing her job.

Non-praise: ZC2 apparently is not

Thre, happy now?

.....Bob
--- GEcho/32 & IM 2.50
* Origin: http://www.fidonet.ca (1:140/12)

From Bob Seaborn@1:140/12 to Ward Dossche on Fri Nov 10 18:50:02 2017

Bob,

Then ward is not doing his job (as usual), my domain changed quite

someBS> 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...

I could care less what you do, especially when you start spewing brown $#!t.

Based on what I've read, you owe your denziens a major apology.
--- GEcho/32 & IM 2.50
* Origin: http://www.fidonet.ca (1:140/12)

From Ward Dossche@2:292/854 to Bob Seaborn on Sat Nov 11 11:01:05 2017

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-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)

From Kees van Eeten@2:280/5003.4 to Bob Seaborn on Sat Nov 11 11:04:50 2017

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.

Non-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)

From Tommi Koivula@2:221/6 to Bob Seaborn on Sat Nov 11 12:25:30 2017

Hi Bob.

10 Nov 17 18:48:00, you wrote to Kees van Eeten:

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

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

---------- 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)

From Ward Dossche@2:292/854 to Tommi Koivula on Sat Nov 11 12:07:32 2017

Tommi,

If I search the zone2 dailylists for 'nwstar.tzo.com' sometimes it is there, sometimes it is not:

The information you see is what I get in the ZONE1-list. If that is erratic, then erratic information is passed on. Z3 and Z4 encounter the same issue.

\%/@rd
--- D'Bridge 3.99
* Origin: I will always keep a PC running WinXP (2:292/854)

From Wilfred van Velzen@2:280/464 to Bob Seaborn on Sat Nov 11 12:11:54 2017

Hi Bob,

On 2017-11-10 18:47: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...

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.
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

From Kees van Eeten@2:280/5003.4 to Ward Dossche on Sat Nov 11 11:47:44 2017

Hello Ward!

11 Nov 17 11:01, you wrote to Bob Seaborn:

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.

I can only speak for the Linux version of makenl-ng, but that is what
ZC1 is using as well. What may be the case, is the following.

The config file where regions are included has lines like:

Region 17 region17.* 1:17/0
or
Region 17 region17 1:17/0

When the first notation is used, makenl will look for segments with the
same productionday as the publishing day of the to be collated nodelist. If it
is not found, makenl will look for the file of the previous week and so
on till a file is found.

In the second notation, makenl will use the segment with the highest
daynumber.

The first notation is not practical for dailylist production as chances are
the there that most region segment will have a daynumber that corresponds with
a Friday.

Apparently the dailylist/zonesegment is run first on Wednesday using the
most recent region segments. The old stucture Wednesday with the Friday
production daynumber is produced from segment files with Friday daynumbers.

The same goes for The Friday nodelist/zonesegment. On friday only one
nodelist/zonesegment is produced from Friday daynumber region segments.

As you use Zone segments in the order they are received, and due to the
differend in publishing time, Zone2 Thursday and Saturday nodelists
produced by you will be based on Zone1 region segment with most recent Friday
daynumbers.

The above is from my understanding of how makenl-ng works.

If nothing changes, it would be wise to ignore Z1 zonesegments with a
Friday daynumber as distributed on Wednesday and Friday.

Kees
--- GoldED+/LNX 1.1.5
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

From Richard Menedetter@2:310/31 to Bob Seaborn on Sat Nov 11 13:35:20 2017

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 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)

From Ward Dossche@2:280/5003.4 to Kees van Eeten on Sat Nov 11 14:07:54 2017

Hello Ward!

11 Nov 17 11:47, I wrote to me:

The config file where regions are included has lines like:

Region 17 region17.* 1:17/0
or
Region 17 region17 1:17/0

I may have messed this up in my previous message, but the gist of the story remains the same.

With '*' as a suffix, a wildcard search is done and the file with the highest
daynumber is used.

Without a suffix, the daynumber of the publication day is used and stepped
back 7 days, when until a file is found. I think it goes back to 6 weeks.

To be really sure, I would have to check on the code of makenl-ng, but
others may know by heart.

Kees
--- GoldED+/LNX 1.1.5
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

From Bob Seaborn@1:140/12 to Ward Dossche on Sat Nov 11 10:14:00 2017

Bob,

Based on what I've read, you owe your denziens a major apology.

You are unable to conduct a well-argumented discussion.

I have no desire to have any such with *you*.

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.

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)

--- GEcho/32 & IM 2.50
* Origin: http://www.fidonet.ca (1:140/12)

From Bob Seaborn@1:140/12 to Tommi Koivula on Sat Nov 11 10:16:01 2017

Hi Bob.

10 Nov 17 18:48:00, you wrote to Kees van Eeten:

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

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.

As it should be, thank you for recognzing this.

If I search the zone2 dailylists for 'nwstar.tzo.com' sometimes it is
there, sometimes it is not:

And we all know who is at fault for this, definitely NOT anyone in z1!

---------- DAILYLST.302

---------- 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)

--- GEcho/32 & IM 2.50
* Origin: http://www.fidonet.ca (1:140/12)

From Bob Seaborn@1:140/12 to Wilfred van Velzen on Sat Nov 11 10:18:02 2017

Hi Bob,

On 2017-11-10 18:47: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...

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!

I have learned over the years to believe very little of what zc2 says!
I have proven him a liar numerous times.

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

--- GEcho/32 & IM 2.50
* Origin: http://www.fidonet.ca (1:140/12)

From Bob Seaborn@1:140/12 to Richard Menedetter on Sat Nov 11 10:19:03 2017

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!

I am not trying to insult anyone, just merely stating what I perceive as the truth.

Based on the evidence in this echo I do not see arguments supporting
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)

--- GEcho/32 & IM 2.50
* Origin: http://www.fidonet.ca (1:140/12)

From Bob Seaborn@1:140/12 to Kees van Eeten on Sat Nov 11 10:14:04 2017

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.

Non-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)

--- GEcho/32 & IM 2.50
* Origin: http://www.fidonet.ca (1:140/12)

From Janis Kracht@1:261/38 to Wilfred van Velzen on Sun Nov 12 01:07:26 2017

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.
--- BBBS/Li6 v4.10 Toy-3
* Origin: Prism bbs (1:261/38)

From Tommi Koivula@2:221/0 to Janis Kracht on Sun Nov 12 10:21:48 2017

12 Nov 17 01:07, Janis Kracht wrote to Wilfred van Velzen:

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.

D:\Nodelist\daily>find /i "bob_sea" DAILYLST.316

---------- DAILYLST.316 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.dynu.net Host,140,Prairie_Net,Saskatchewan_Canada,Bob_Seaborn,-Unpublished-,300 ,CM,MO,MN,XX,IBN:nwstar.dynu.net ,1,nwstar.dynu.net,Saskatchewan,Bob_Seaborn,-Unpublished-,300,CM,MN,XX ,MO,IBN:nwstar.dynu.net,UNEC ,12,Great_White_North,Saskatoon,Bob_Seaborn,-Unpublished-,300,CM,MO

Cool.

Lets wait for tomorrow. :)

'Tommi

--- hpt/os2-emx 1.9.0-cur 17-02-17
* Origin: 2001:470:1f15:cb0:f1d0:2:221:0 (2:221/0)

From Björn Felten@2:203/2 to Janis Kracht on Sun Nov 12 09:25:43 2017

That should take care of the problem.

So it wasn't Ward that was at fault, like someone here claimed over and over
again?

..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se (2:203/2)

From Ward Dossche@2:292/854 to Björn Felten on Sun Nov 12 12:27:40 2017

That should take care of the problem.

So it wasn't Ward that was at fault, like someone here claimed over
and over again?

The word "fault" is heavy handed. Shit has happened to all of us in the past and will happen in future.

What is troublesome however is that someone with a blurred view, to use an understatement, is nominating people and will vote for them after clearly displaying that his technical judgement is way inferior to the size of his mouth.

\%/@rd

--- D'Bridge 3.99
* Origin: I will always keep a PC running WinXP (2:292/854)

From Richard Menedetter@2:310/31 to Janis Kracht on Sun Nov 12 12:30:08 2017

Hi Janis!

12 Nov 2017 01:07, from Janis Kracht -> Wilfred van Velzen:

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.

Thank you Janis for fixing it!

To put it in the words of a fellow node here, whose fault was it??
Or to put it in his words:
"I could care less what you do, especially when you start spewing brown $#!t."

I would have preferred if the whole shit spewing mails could have been omitted. It is not good for the network.

I really do not understand why people go on such tangents, and immediately make
(false) assumptions, instead of simply waiting for you to clarify ...

CU, Ricsi

--- GoldED+/LNX
* Origin: I am Homer of Borg! Prepare to be... Oooooo! Donuts! (2:310/31)

From Wilfred van Velzen@2:280/464 to Tommi Koivula on Sun Nov 12 13:26:32 2017

Hi Tommi,

On 2017-11-12 10:21:48, you wrote to Janis Kracht:

Lets wait for tomorrow. :)

Lets wait for the weekly... ;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

From Tommi Koivula@2:221/1 to Wilfred van Velzen on Sun Nov 12 17:55:00 2017

12 Nov 17 13:26:32, you wrote to me:

On 2017-11-12 10:21:48, you wrote to Janis Kracht:

Lets wait for tomorrow. :)

Lets wait for the weekly... ;)

That also, but tomorrow first. ;-)

'Tommi

---
* Origin: telnet://v6.fidonet.fi (2:221/1)

From Ward Dossche@2:292/854 to Tommi Koivula on Sun Nov 12 18:53:27 2017

Lets wait for tomorrow. :)

Lets wait for the weekly... ;)

That also, but tomorrow first. ;-)

That's not what the lady said. She said "Tomorrow is another day".

\%/@rd

--- D'Bridge 3.99
* Origin: I will always keep a PC running WinXP (2:292/854)

From Kees van Eeten@2:280/5003.4 to Bob Seaborn on Sat Nov 11 23:53:02 2017

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.

Kees

--- GoldED+/LNX 1.1.5
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

From Bob Seaborn@1:140/12 to Kees van Eeten on Sun Nov 12 14:15:00 2017

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!

.....Bob

--- GEcho/32 & IM 2.50
* Origin: http://www.fidonet.ca (1:140/12)

From Kees van Eeten@2:280/5003.4 to Bob Seaborn on Mon Nov 13 00:16:32 2017

Hello Bob!

12 Nov 17 14:15, you wrote to me:

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.

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.

Thanks,

Kees

--- GoldED+/LNX 1.1.5
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

From Bob Seaborn@1:140/12 to Kees van Eeten on Sun Nov 12 19:07:00 2017

Hello Bob!

12 Nov 17 14:15, you wrote to me:

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.

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

Thank you.

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.

Considering that ward has proven to myself, and others over here that 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.

.....Bob

--- GEcho/32 & IM 2.50
* Origin: http://www.fidonet.ca (1:140/12)

From Jeff Smith@1:282/1031 to All on Sun Nov 12 19:04:42 2017

Hello There,

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"?

Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: The Ouija Board (1:282/1031)

From Ward Dossche@2:292/854 to Jeff Smith on Mon Nov 13 02:27:21 2017

Hi Jeff,

Do we not have the ability to say and
realize that "OK, Shit Happened. Lets fix it and move on"?

You mean as in ...

**************************************************************************** Date: 12 Nov 17 12:27:40
From: Ward Dossche
To: Björn Felten
Subj: Re: Z1 weekly nodelist segment in Z2 nodelist ____________________________________________________________________________ Shit has happened to all of us in the past and will happen in future. ****************************************************************************

??

\%/@rd

--- D'Bridge 3.99
* Origin: I will always keep a PC running WinXP (2:292/854)

From Richard Menedetter@2:310/31 to Bob Seaborn on Mon Nov 13 09:43:14 2017

Hi Bob!

12 Nov 2017 19:07, from Bob Seaborn -> Kees van Eeten:

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.

Considering that ward has proven to myself, and others over here that
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 would help tremendously, if you would asses the evidence before you blame anybody.

So you would have much more credibility!

CU, Ricsi

--- GoldED+/LNX
* Origin: Action is the antidote to despair. (2:310/31)

From Richard Menedetter@2:310/31 to Jeff Smith on Mon Nov 13 09:49:06 2017

Hi Jeff!

12 Nov 2017 19:04, from Jeff Smith -> All:

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"?

I think this is what happened.
Janis was made aware of a problem.
She was away from keyboard, and as soon as she was back she fixed it, and reported back that it was fixed.

The issue is that one person jumped to conclusions extremely prematurely, and without evidence.

I really hope that personal animosity will have less room in the future of fidonet.

CU, Ricsi

--- GoldED+/LNX
* Origin: I've got a very bad feeling about this... (2:310/31)

From Tommi Koivula@2:221/0 to Janis Kracht on Sun Nov 12 10:21:48 2017

12 Nov 17 01:07, Janis Kracht wrote to Wilfred van Velzen:

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.

D:\Nodelist\daily>find /i "bob_sea" DAILYLST.316

---------- DAILYLST.316 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.dynu.net Host,140,Prairie_Net,Saskatchewan_Canada,Bob_Seaborn,-Unpublished-,300 ,CM,MO,MN,XX,IBN:nwstar.dynu.net ,1,nwstar.dynu.net,Saskatchewan,Bob_Seaborn,-Unpublished-,300,CM,MN,XX ,MO,IBN:nwstar.dynu.net,UNEC ,12,Great_White_North,Saskatoon,Bob_Seaborn,-Unpublished-,300,CM,MO

Cool.

Lets wait for tomorrow. :)

'Tommi

--- hpt/os2-emx 1.9.0-cur 17-02-17
* Origin: 2001:470:1f15:cb0:f1d0:2:221:0 (2:221/0)

From Björn Felten@2:203/2 to Janis Kracht on Sun Nov 12 09:25:43 2017

That should take care of the problem.

So it wasn't Ward that was at fault, like someone here claimed over and over
again?

..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se (2:203/2)

From Ward Dossche@2:292/854 to Björn Felten on Sun Nov 12 12:27:40 2017

That should take care of the problem.

So it wasn't Ward that was at fault, like someone here claimed over
and over again?

The word "fault" is heavy handed. Shit has happened to all of us in the past and will happen in future.

What is troublesome however is that someone with a blurred view, to use an understatement, is nominating people and will vote for them after clearly displaying that his technical judgement is way inferior to the size of his mouth.

\%/@rd

--- D'Bridge 3.99
* Origin: I will always keep a PC running WinXP (2:292/854)

From Richard Menedetter@2:310/31 to Janis Kracht on Sun Nov 12 12:30:08 2017

Hi Janis!

12 Nov 2017 01:07, from Janis Kracht -> Wilfred van Velzen:

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.

Thank you Janis for fixing it!

To put it in the words of a fellow node here, whose fault was it??
Or to put it in his words:
"I could care less what you do, especially when you start spewing brown $#!t."

I would have preferred if the whole shit spewing mails could have been omitted. It is not good for the network.

I really do not understand why people go on such tangents, and immediately make
(false) assumptions, instead of simply waiting for you to clarify ...

CU, Ricsi

--- GoldED+/LNX
* Origin: I am Homer of Borg! Prepare to be... Oooooo! Donuts! (2:310/31)

From Wilfred van Velzen@2:280/464 to Tommi Koivula on Sun Nov 12 13:26:32 2017

Hi Tommi,

On 2017-11-12 10:21:48, you wrote to Janis Kracht:

Lets wait for tomorrow. :)

Lets wait for the weekly... ;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

From Kees van Eeten@2:280/5003.4 to Bob Seaborn on Mon Nov 13 11:58:34 2017

Hello Bob!

12 Nov 17 19:07, you wrote to me:

I honestly doubt that it will be settled very soon, however
our concerns have been noted.

Sad.

Kees

--- GoldED+/LNX 1.1.5
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

From Wilfred van Velzen@2:280/464 to Janis Kracht on Fri Nov 17 12:26:07 2017

Hi Janis,

On 2017-11-12 01:07:26, you wrote to me:

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.

Bye, Wilfred.

=== 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,INA :the-estar.com,IBN

4c4
< ,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,33600 ,TEW,ICM,XA,V32b,V42b,H16,V32t,V34,IBN:wpusa.dynip.com,ITN,IVM,IFT

82,83c82,83
< ,545,Rocasa_FTN_Testing,Lansing_MI,RJ_Clay,000-198-37-102-11,300,XA,CM,INA:ftn.rocasa.com,IBN:24555,IFC,ITN:60177,PING,U,IPv6
< Down,546,Rocasa_BBBS,Lansing_MI,Robert_Clay,-Unpublished-,300,XX,CM,INA:bbbs.rocasa.biz,IBN,IUC:filebot@rocasa.biz
-+-

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.biz

148c148
< Host,229,Greater_Toronto_Area,Toronto_ON,Nick_Andre,1-647-847-2083,9600,CM,XX,INA:bbs.darkrealms.ca,IBN,ICM
-+-

Host,229,West_ON/Toronto/GTA,Toronto_ON,Nick_Andre,1-647-847-2083,9600,CM ,XX,INA:bbs.darkrealms.ca,IBN,ICM

161c161
< Host,249,Lake_Ontario_Net_(Interim_NC),Toronto_ON,Nick_Andre,1-647-847-2083,9600,CM,XX,INA:bbs.darkrealms.ca,IBN,ICM
-+-

Host,249,East_ON/PQ/NB/PE/NS/NF,Montreal_Quebec,Luc_Mccarragher,-Unpublis hed-,300,CM,IBN:mccarragher.org

246,247c246,247
< Hub,300,RVA_Fido_Support,Richmond_VA,Ozz_Nixon,-Unpublished-,300,CM,XX,INA:fido.pwnz.org,IBN,ITN,IFT
< ,362,RVA_Fido_Support,Richmond_VA,Ozz_Nixon,-Unpublished-,300,CM,XX,INA:fido.pwnz.org,IBN,ITN,IFT
-+-

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,IFT

249,250c249,250
< Region,14,Mid_West,IA_KS_MN_MO_NE_ND_SD,Jeff_Smith,-Unpublished-,300,CM,MO,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,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,IBN

253,254c253,254
< 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, 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

260a261

,1059,Temple_Of_Syrinx,St_Paul_MN,Daniel_Kidd,-Unpublished-,300,CM,XX,IBN ,ITN,,INA:templeofsyrinx.info

263c264,273
< 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-,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-,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

267c277
< 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,INA :bbs.ouijabrd.net,IBN

272,274c282,284
< 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,-Unpublished-,9600,CM,XX,H16,V32b,V42b,V34,V32t,X2C,INA:region15.net,IBN:24554,IFT,ITN
< ,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,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:24554

299a310

,706,RPG_Circus_BBS,Mesa_AZ,Jeffrey_Brissette,-Unpublished-,9600,CM,XX,H1 6,V32b,V42b,V34,V32t,X2C,INA:162.208.11.127,IBN

410c421
< 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_lewis ,1-919-774-5930,33600,XA,V34,CM,ITN,INA:ftn.wpusa.dynip.com,IBN,IVM,PING

477c488
< Host,3634,North_Carolina_USA_(2017/319),central_NC_USA,mark_lewis,1-919-774-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-7 74-5930,33600,XA,V34,CM,ITN,INA:ftn.wpusa.dynip.com,IBN,IVM,PING

522a534

,5016,End_Of_The_Line_BBS,Plano_Tx,Nigel_Reed,-Unpublished-,300,CM,XA,INA :ipv4.endofthelinebbs.com:2300,IBN:ipv4.endofthelinebbs.com:24554

546d557
< ,75,Positronium_Mystic_Pi,Lafayette_LA,Ben_Ritchey,-Unpublished-,300,CM,XX,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)

From Wilfred van Velzen@2:280/464 to Tommi Koivula on Fri Nov 17 12:31:15 2017

Hi Tommi,

On 2017-11-12 17:55:00, you wrote to me:

Lets wait for tomorrow. :)

Lets wait for the weekly... ;)

That also, but tomorrow first. ;-)

Regarding the weekly, Janis will have to redo her homework! :-(

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

From Tommi Koivula@2:221/1 to Wilfred van Velzen on Fri Nov 17 18:46:52 2017

Hi Wilfred.

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.

'Tommi

---
* Origin: telnet://v6.fidonet.fi (2:221/1)

From Wilfred van Velzen@2:280/464 to Tommi Koivula on Fri Nov 24 12:55:26 2017

Hi Tommi,

On 2017-11-17 18:46:52, you wrote to me:

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. GIGO...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

From Wilfred van Velzen@2:280/464 to Janis Kracht on Fri Nov 24 12:50:50 2017

* Originally in ZCC-PUBLIC
* Crossposted in FN_SYSOP

Hi Janis,

On 2017-11-17 12:26:07, I wrote to you:

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.

A week later and the problem still exists. There were about a dozen real changes in the Z1 segment in the Z1 weekly nodelist compared to last week. There were none in the Z1 segment of the Z2 nodelist. So the differences actually got worse. :-(

Janis please do your work!

=== 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,INA
:the-estar.com,IBN

4c4
< ,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,33600
,TEW,ICM,XA,V32b,V42b,H16,V32t,V34,IBN:wpusa.dynip.com,ITN,IVM,IFT

82,83c82,83
< ,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: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.biz

148c148
< 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,CM
,XX,INA:bbs.darkrealms.ca,IBN,ICM

161c161
< 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,-Unpublis
hed-,300,CM,IBN:mccarragher.org

246,247c246,247
< 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,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,IFT

249,250c249,250
< 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,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,IBN

253,254c253,254
< 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,
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

260a261

,1059,Temple_Of_Syrinx,St_Paul_MN,Daniel_Kidd,-Unpublished-,300,CM,XX,IBN
,ITN,,INA:templeofsyrinx.info

263c264,273
< 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-,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-,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

267c277
< 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,INA
:bbs.ouijabrd.net,IBN

272,274c282,284
< 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,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:24554

299a310

,706,RPG_Circus_BBS,Mesa_AZ,Jeffrey_Brissette,-Unpublished-,9600,CM,XX,H1
6,V32b,V42b,V34,V32t,X2C,INA:162.208.11.127,IBN

410c421
< 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_lewis
,1-919-774-5930,33600,XA,V34,CM,ITN,INA:ftn.wpusa.dynip.com,IBN,IVM,PING

477c488
< 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-7
74-5930,33600,XA,V34,CM,ITN,INA:ftn.wpusa.dynip.com,IBN,IVM,PING

522a534

,5016,End_Of_The_Line_BBS,Plano_Tx,Nigel_Reed,-Unpublished-,300,CM,XA,INA
:ipv4.endofthelinebbs.com:2300,IBN:ipv4.endofthelinebbs.com:24554

546d557
< ,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)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

From Tommi Koivula@2:221/1 to Wilfred van Velzen on Fri Nov 24 14:11:32 2017

24 Nov 17 12:55:26, you wrote to me:

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.

Yes of course but then there is only one thing to look after.

'Tommi

---
* Origin: telnet://v6.fidonet.fi (2:221/1)

From Janis Kracht@1:261/38 to Wilfred van Velzen on Fri Nov 24 11:10:46 2017

,20,The_North_American_Backbone,Zone_1,NAB,-Unpublished-,300,CM,MO,XX,INA >>> :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:cmech .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

Stop wasting my time!

--- BBBS/Li6 v4.10 Toy-3
* Origin: Prism bbs (1:261/38)

From Wilfred van Velzen@2:280/464 to Janis Kracht on Mon Nov 27 10:45:41 2017

* Originally in ZCC-PUBLIC
* Crossposted in FN_SYSOP

Hi Janis,

On 2017-11-24 11:10:46, you wrote to me:

,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

That's right, this was the compare of the .321 nodelists where the "estar" entry was in the Z1 nodelist. That was fixed, but in last weeks .328 nodelists there are still a lot of differences. Here are two nice visual compares between
the two, for your convenience. Left is the Z1 version, on the right the Z2:

https://www.diffchecker.com/zPTaovpr

or:

https://www.diffnow.com/?report=wptsb
(more details...)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Who's Online

System Info

Sysop:	digital man
Location:	Riverside County, California
Users:	1,049
Nodes:	15 (0 / 15)
Uptime:	48:57:46
Calls:	236,052
Files:	60,364
D/L today:	10 files (440K bytes)
Messages:	289,574

Z1 weekly nodelist segment in Z2 nodelist

Who's Online

System Info