Nп/п : 51 из 90
От : Nick Boel 1:154/700 23 апр 26 17:30:51
К : Mike Powell 23 апр 26 01:38:02
Тема : Re: htick "issue"
----------------------------------------------------------------------------------
@MSGID: 2624.fidosoft@1:154/700 2e4fdddb
@REPLY: 43.husky@1:2320/107 2e4f6ca4
@TZUTC: -0500
@PID: Synchronet 3.22a-Linux master/9019e4bcb Apr 20
2026 GCC 15.2.1
@TID: SBBSecho 3.37-Linux master/9019e4bcb Apr 20
2026 GCC 15.2.1
@BBSID: PHARCYDE
@CHRS: UTF-8 4
@FORMAT: flowed
@NOTE: Mozilla/5.0 (Windows NT 10.0; Win64; x64;
rv:140.0) Gecko/20100101Thunderbird/140.9.1
Hey Mike!
On Thu, Apr 23 2026 10:10:49 -0500, you wrote:
> Is there a way to get htick to ignore these issues and go ahead and
> process the files?
> 7 00:20:01 Processing Tic-File /home/bbs/fido/inbound/0urbuzff.tic
> 7 00:20:01 File "db4s.zip": size: 2751653, area: DBRIDGE, from:
> 1:154/10, orig: 7 00:20:01 Size of file `/home/bbs/fido/inbound/
> db4s.zip` differs with TIC. I t A 00:20:01 Can`t check size of file
> "db4s.zip": No such file or directory. Skip A 00:20:01 Can`t check
> size of file "db4s.zip.1": No such file or directory. Sk A 00:20:01
> Can`t check size of file "db4s.zip.2": No such file or directory. Sk
> 7 00:20:01 Wrong CRC for file "db4s.zip", skipping this file (in
> tic:ef043450,
> I tried adding the `-b` parameter but that does not address
issues> such as these.
In the last line, it says "in tic: ef043450". This doesn`t seem to
match the original tic that came from my system (0urbuzff.tic), which is
most likely why there was a CRC issue.
Are you getting this file and/or fileecho from multiple hubs? It
seems you have 3 of the same file that overwrote each other, and it
looks like you (or htick) deleted all three of them at some point?
Almost seems like before the original .tic was processed, you got
another tic and the same db4s.zip from another system, and then possibly
even another one after that.
If you still have a file named "db4s.zip", that may not be the
one that came with the .tic file that is being processed. If you do
have multiple file hubs for the same fileechos, I`d recommend not doing
that. While it works with echomail (because of dupe checking), I`m not so
sure it works very well with files.
Regards,
Nick
... Sarcasm, because beating people up is illegal.
--- SBBSecho 3.37-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)
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 3634/12 5000/111
SEEN-BY: 5010/352 5015/46 5020/715 828 846 848
1042 4441 12000 5030/49 1081
SEEN-BY: 5053/51 5061/133 5075/128 5083/444
@PATH: 154/700 10 221/6 5020/1042 4441