Now using 1.0.7 with file pass-thru areas and just noticed a problem.
File area PASCLNET is pass-thru and this is showing log for
processing:
-!-
10-Apr-2017 00:00:10 mbfido[8735] MBFIDO v1.0.7
10-Apr-2017 00:00:10 mbfido[8735] Cmd: mbfido tic toss web -quiet
+ 10-Apr-2017 00:00:10 mbfido[8735] Pass: hatch files
+ 10-Apr-2017 00:00:10 mbfido[8735] Pass: process ticfiles (/home/mbse/var/inbound)
+ 10-Apr-2017 00:00:10 mbfido[8735] Processing bb7e2e6f.tic,
PASNDLST.Z99 area PASCLNET from 1:261/38 + 10-Apr-2017 00:00:10 mbfido[8735] +- by BBBS/Li6 v4.10 Toy-3 + 10-Apr-2017 00:00:10 mbfido[8735] 8.3 name "PASNDLST.Z99", LFN "pasndlst.z99" + 10-Apr-2017 00:00:10 mbfido[8735] Passthru TIC area! + 10-Apr-2017 00:00:10 mbfido[8735] Scanning /home/mbse/var/inbound/PASNDLST.Z99 with Clam AntiVirus stream scanner + 10-Apr-2017 00:00:10 mbfido[8735] Trying
IPv4 127.0.0.1 port 3310 + 10-Apr-2017 00:00:10 mbfido[8735] No banner command for + 10-Apr-2017 00:00:13 mbfido[8735] Execute: /usr/bin/rm
-r -f arc8735 + 10-Apr-2017 00:00:13 mbfido[8735] Forward file to 2:230/35@fidonet without netmail + 10-Apr-2017 00:00:14 mbfido[8735] Forward file to 2:250/9@fidonet without netmail + 10-Apr-2017 00:00:14 mbfido[8735] Processing bb7e2e8d.tic, PASNDLST.099 area PASCLNET from 1:261/38 + 10-Apr-2017 00:00:14 mbfido[8735] +- by BBBS/Li6 v4.10
Toy-3 + 10-Apr-2017 00:00:14 mbfido[8735] 8.3 name "PASNDLST.099", LFN
"pasndlst.099" + 10-Apr-2017 00:00:14 mbfido[8735] Passthru TIC area!
? 10-Apr-2017 00:00:14 mbfido[8735] Duplicate file
+ 10-Apr-2017 00:00:14 mbfido[8735] Moving /home/mbse/var/inbound/bb7e2e8d.tic to
/home/mbse/var/badtic/bb7e2e8d.tic + 10-Apr-2017 00:00:14 mbfido[8735] Moving /home/mbse/var/inbound/PASNDLST.099 to /home/mbse/var/badtic/PASNDLST.099 + 10-Apr-2017 00:00:14 mbfido[8735] Pass: hatch files + 10-Apr-2017 00:00:14 mbfido[8735] Pass: process ticfiles (/home/mbse/var/inbound) + 10-Apr-2017 00:00:14 mbfido[8735] Pass: toss netmail (/home/mbse/var/inbound) + 10-Apr-2017 00:00:14 mbfido[8735] Pass: toss ARCmail (/home/mbse/var/inbound) + 10-Apr-2017 00:00:14 mbfido[8735] Start making statistic HTML pages + 10-Apr-2017 00:00:14 mbfido[8735] Finished making statistic HTML pages +
10-Apr-2017 00:00:14 mbfido[8735] Flushing outbound queue +
10-Apr-2017 00:00:14 mbfido[8735] Route to 2:250/9@fidonet via 2:250/9@fidonet
+ 10-Apr-2017 00:00:14 mbfido[8735] Adding files for 2:250/9@fidonet
via
2:250/9@fidonet
? 10-Apr-2017 00:00:14 mbfido[8735] attach: file /home/mbse/var/inbound/PASNDLST.Z99 failed, No such file or directory
+ 10-Apr-2017 00:00:14 mbfido[8735] Route to 2:230/35@fidonet via 2:230/35@fidonet
+ 10-Apr-2017 00:00:14 mbfido[8735] Adding files for 2:230/35@fidonet
via
2:230/35@fidonet
? 10-Apr-2017 00:00:14 mbfido[8735] attach: file /home/mbse/var/inbound/PASNDLST.Z99 failed, No such file or directory
+ 10-Apr-2017 00:00:14 mbfido[8735] TICfiles [ 2] import [ 0] out
[ 2] bad [ 1] dupe [ 1] -!-
If you look near the botton you will see that after tossing mbfido is trying to attached file to two downlinks but cannot find the file (PASNDLST.Z99) in the ~/var/inbound directory.
Looks like it deleted it before finishing the tossing & attaching processing steps.
The above situation is the same for other instances with the same file area and files.
Does it make sense ?
There does appear to be a problem. Apparently if a file is seen as a duplicate, it is immediately moved to the badtic directory. It
shouldn't be trying to forward it to downlinks if it's a duplicate
file. I'll have to dig further into the .TIC file code and get that sorted out.
On 2017 Apr 13 19:32:54, you wrote to Vince Coen:
There does appear to be a problem. Apparently if a file is seen
as a duplicate, it is immediately moved to the badtic directory.
It shouldn't be trying to forward it to downlinks if it's a
duplicate file. I'll have to dig further into the .TIC file code
and get that sorted out.
shouldn't it be up to each system to determine what is a duplicate
file and what is not? why should the contents of my files areas
influence what files you have? that's what you appear to be saying
should be done... so if i create a file named mbse42.zip and a new
official version 4.2 is hatched with the same name, those downstream
from me won't get it even though they never had it and it only existed
on my system until the new release was hatched... plus i might be
greatly upset if my mbse42.zip were overwritten causing the loss of
the information stored in it...
In the example I gave mbse often says the pasdnlst.nnn or .znn are
dups when the .ext's are different. I would suggest that it may well
only be comparing the filename without the .ext taken into
consideration.
Only happens with this file areas as these are daily nodelists.
Blasted things are a pest.
Only happens with this file areas as these are daily nodelists.
Blasted things are a pest.
Only happens with this file areas as these are daily nodelists.
do you also carry the DAILYLIST area?
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,034 |
Nodes: | 15 (0 / 15) |
Uptime: | 137:46:06 |
Calls: | 669 |
Calls today: | 3 |
Files: | 95,163 |
D/L today: |
603 files (105M bytes) |
Messages: | 297,608 |