= Сообщение: 2869 из 12519 ====================================== ENET.SYSOP = От : Björn Felten 2:203/2 29 Sep 15 17:50:51 Кому : Kees van Eeten 29 Sep 15 17:50:51 Тема : The DAILYLST FGHI : area://ENET.SYSOP?msgid=2:203/2+560ab35a На : area://ENET.SYSOP?msgid=2:280/5003.4+560aa9db = Кодировка сообщения определена как: CP437 ================================== Ответ: area://ENET.SYSOP?msgid=2:280/5555+560ac24d ============================================================================== KvE> In general the dailylist is not updated, when a region update arrives. But KvE> there are sections that are maintained manually by the ZC.
Yeah, so what? When the daily (as in once a day) list is issued all is fine.
KvE> I still fail to see the problem.
BOC. Nobody has talked about a problem here. I stated that I found some oddities in my original message, didn't I?
I've even recently recommended the former Scandinavian RCs (now NCs) to get the file echo from 2:203/0 so that by the time they get it my system has sorted out all the erroneous files and TICs.
KvE> At the start it was explained that the file could be hatched more then once KvE> a day.
NO IT WAS NOT!!!!
If it had, I for one would vigorously have objected to something stupid like that. And by now you should be aware of the fact that e.g. Benny too never has heard about this. And he's the one that repeatedly has reported errors (N.B. *not* problems) in the file echo.
KvE> What I would like to tune in on is what happened at your system and KvE> probably KvE> happens at Bennys system as well, the deliveries within 40 secs.
What happens is hatching 1.01. Fido hatching must always be done in a linear process. If you have several tasks that intervenes, our old FTN programs will inevitably run into problems now and then.
KvE> some time, and maybe timeouts are reached.
I seriously doubt that. It's more likely that Ward runs different batch files, that does not take into account what has happened earlier in the process.
Files have been moved or altered when the actual TIC files are sent (we've recently seen reports of files being different in various depositories), and then all kind of *oddities* are bound to happen.
KvE> But what happens if the file processing is initiated by binkd directly KvE> after the session is closed?
FYI, all inbound mail are received by Argus here, and not binkd.
--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125 * Origin: news://felten.yi.org (2:203/2)
