= Сообщение: 2911 из 12519 ====================================== ENET.SYSOP = От : Kees van Eeten 2:280/5003.4 30 Sep 15 20:29:04 Кому : Benny Pedersen 30 Sep 15 20:29:04 Тема : The DAILYLST FGHI : area://ENET.SYSOP?msgid=2:280/5003.4+560c2cad На : area://ENET.SYSOP?msgid=2:230/38.1+ad8b2229 = Кодировка сообщения определена как: LATIN-1 ================================ ============================================================================== Hello Benny!
30 Sep 15 18:05, you wrote to me:
KV>> with the same file name to transport. One will the first will KV>> have a false CRC, if the second nodelist is indeed different.
BP> yes you got it :)
BP> if tossers is more smart with find the matching file in inbound based on BP> crc, huh ?, the tosser could toss with the filename in tic file, but BP> select the file in inbound with matching crc
BP> no one have coded this yet, so not supported
Maybe not, but on my system the problem is not new. It has existed as long as there were two distributions of the fidonews. Often both were in the inbound at the same time. After a run with the file tusser, I was stuck with one renamed fidonews ( renamed by binkd on reception ) and a tickfile renamed to .bad. A script then renames the fidonews file to its original name and restores the suffix of the tickfile to .tic. You can include a check on the filename and the crc, as well as the origin of the tick file. I used the latter to decide wich edition has handeled. After this renaming the filetosser is run again.
I have some other situations, where I made similar arrangements.
Kees
--- GoldED+/LNX 1.1.5 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
