Nп/п : 44 из 100
От : Mike Powell 1:2320/107 25 апр 26 10:24:00
К : NICK BOEL 25 апр 26 18:33:01
Тема : Re: htick "issue"
----------------------------------------------------------------------------------
@MSGID: 55.husky@1:2320/107 2e5212c7
@REPLY: 2631.fidosoft@1:154/700 2e515b20
@TZUTC: -0500
@PID: Synchronet 3.21a-Linux master/123f2d28a Jul 12
2025 GCC 12.2.0
@TID: SBBSecho 3.28-Linux master/123f2d28a Jul 12
2025 GCC 12.2.0
@BBSID: CAPCITY2
@CHRS: ASCII 1
@FORMAT: flowed
> Typically, the first "db4s.zip" that would arrive on your system would use the
> REPLACES tag and replace your upper case one. From then on out, it would
> overwrite the latest lowercase one. This shouldn`t be an issue if the first on
> was processed before the others arrived.
But then when the next db4s.zip arrives, there is no uppercase one to
replace. It looks to me like it won`t replace the lowercase
dataset name, leaving the old (lowercase) one out there to cause a mismatch
later.
> I don`t think the REPLACES tag causes errors. It would just look for a DB4S.ZI
> and replace it, if it`s not there, it would process it and your directory woul
> then maybe include two files, one uppercase and the other lowercase.
I think it might cause an issue when the file already exists and it cannot
replace it because the filename doesn`t match. It then eventually tries to
match a new tic with the older dataset, which is what happened here.
> What I saw in your log was that it wasn`t using the proper .tic file for the
> "db4s.zip" that was in your inbound. For example, the original db4s.zip was
> still there, the next two that arrived were renamed. The latest .tic file (the
> one that came with the file that was renamed to "db4s.zip.2" to arrive was
> being used on the old file, so that`s where the CRC/filesize errors were
> occurring.
That would make sense, since it was trying to match to "db4s.zip" and the
one it was finding was the old one from September.
> It`s all good. As I mentioned in the previous message, delete all of them and
> the .tic files, grab it again with the filefix command I gave you. We`ll see
> what happens next release.
I got it processed "by hand." ;) If that echo continues causing issues, I
will just drop it.
* SLMR 2.1a * Mason-Dixon Line n. Separates y`all from youse guys
--- SBBSecho 3.28-Linux
* Origin: Capitol City Online (1:2320/107)
SEEN-BY: 19/10 50/109 104/117 119 114/10 120/616
153/757 154/10 30 50 700
SEEN-BY: 218/840 220/20 90 221/1 6 360 226/18 20
44 50 280/464 301/1 335/364
SEEN-BY: 341/66 234 452/28 166 460/58 463/68
2320/105 106 107 304 3634/12
SEEN-BY: 5000/111 5010/352 5015/46 5020/715 828 846
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5053/51 5061/133 5075/128
5083/444 12320/7
@PATH: 2320/107 105 154/10 221/6 5020/1042 4441