Vincent Coen wrote to All <=-

Problem is it is NOT doing any replacing.

That's really odd. Is the TIC file being created correctly?

-- Sean

... My friend David just had his ID stolen. Now he's just Dav.
___ MultiMail/Linux v0.52

--- Maximus/2 3.01
* Origin: Outpost BBS - bbs.outpostbbs.net:10323 (1:18/200)

Hello Sean!

Saturday July 08 2023 16:32, you wrote to me:

Vincent Coen wrote to All <=-

Problem is it is NOT doing any replacing.

That's really odd. Is the TIC file being created correctly?

-- Sean

... My friend David just had his ID stolen. Now he's just Dav.
___ MultiMail/Linux v0.52

Looks ok - I do not have any generated tics in var/ticqueue so cannot check it but I am sure I will get another file for tossing in the next few days and I will re-reply to you when that happens.

Just had a quick check for the tracing debug flags etc but none for this purpose - unless you know different that is :)

If it helps the system log shows :

08-Jul-2023 15:04:18 mbseq[1602540] MBSEQ v1.0.8.4
+ 08-Jul-2023 15:04:18 mbseq[1602540] Sequence string 476c360e
08-Jul-2023 15:04:18 mbseq[1602540] MBSEQ finished
08-Jul-2023 15:04:18 mbfido[1602542]
08-Jul-2023 15:04:18 mbfido[1602542] MBFIDO v1.0.8.4
08-Jul-2023 15:04:18 mbfido[1602542] Cmd: mbfido tic
+ 08-Jul-2023 15:04:18 mbfido[1602542] Pass: hatch files
+ 08-Jul-2023 15:04:18 mbfido[1602542] Pass: process ticfiles (/home/mbse/var/in
bound)
+ 08-Jul-2023 15:04:18 mbfido[1602542] Processing 476c360e.tic, QBSHELLF.ZIP are
a PDNBASIC from 2:250/1
+ 08-Jul-2023 15:04:18 mbfido[1602542] +- MBSE BBS hatch script v1.0.3
+ 08-Jul-2023 15:04:18 mbfido[1602542] Replace QBSHELL*.ZIP
+ 08-Jul-2023 15:04:18 mbfido[1602542] 8.3 name "QBSHELLF.ZIP", LFN "QBSHELLF.ZI
P"
+ 08-Jul-2023 15:04:18 mbfido[1602542] CRC: missing, calculating CRC
+ 08-Jul-2023 15:04:18 mbfido[1602542] No active virus scanners, skipping scan + 08-Jul-2023 15:04:18 mbfido[1602542] Execute: /home/mbse/bin/unzip -o -j -L /h
ome/mbse/var/inbound/QBSHELLF.ZIP FILE_ID.DIZ
+ 08-Jul-2023 15:04:19 mbfido[1602542] Execute: /home/mbse/bin/unzip -o -j -L /h
ome/mbse/var/inbound/QBSHELLF.ZIP file_id.diz
+ 08-Jul-2023 15:04:19 mbfido[1602542] Execute: /usr/bin/zip -z < ~/etc/banner.t
xt /home/mbse/var/inbound/QBSHELLF.ZIP
+ 08-Jul-2023 15:04:20 mbfido[1602542] New banner banner.txt
+ 08-Jul-2023 15:04:20 mbfido[1602542] Execute: /usr/bin/rm -r -f arc1602542
+ 08-Jul-2023 15:04:20 mbfido[1602542] Import: QBSHELLF.ZIP (QBSHELLF.ZIP) Area:
PDNBASIC
+ 08-Jul-2023 15:04:20 mbfido[1602542] Forward file to 1:261/38@fidonet without
netmail
+ 08-Jul-2023 15:04:20 mbfido[1602542] Forward file to 1:317/3@fidonet without netmail


Not a mention. but in debug some extra logging :

08-Jul-2023 15:04:24 mbfile[1602552] MBFILE v1.0.8.4
08-Jul-2023 15:04:24 mbfile[1602552] Command line: mbfile index -quiet
+ 08-Jul-2023 15:04:24 mbfile[1602552] FREQ. Areas [ 167] Files [ 10431] Updated [ 1]
+ 08-Jul-2023 15:04:24 mbfile[1602552] Index Areas [ 169] Files [ 10449] Updated [ 1]
+ 08-Jul-2023 15:04:24 mbfile[1602552] HTML Areas [ 169] Files [ 10449] Updated [ 1]
08-Jul-2023 15:04:24 mbfile[1602552] MBFILE finished in 0.00s


but as it only shows Updated and not replaced - not helpful really.

Have to wait for a new hatch.


Vincent

--- Mageia Linux v8 X64/Mbse v1.0.8.3/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Hello Sean!

Saturday July 08 2023 16:32, you wrote to me:

Vincent Coen wrote to All <=-

Problem is it is NOT doing any replacing.

That's really odd. Is the TIC file being created correctly?

Here is the new one for area PDNBASIC, again it has not replaced the older one's.

--
Area PDNBASIC
Origin 2:250/1
From 2:250/1
Replaces QBSHELL*.ZIP
File QBSHELLG.ZIP
Lfile QBSHELLG.ZIP
Size 880997
Desc QB64shell v.0001 r.001 for Windows release 07/01/2023
Crc 17C46B3C
Areadesc PDN: Basic Related
Fdn PDN - Programmers Distribution Network
Created by MBSE BBS 1.0.8.4 Copyright (C) 1997-2023 MBSE DevTm
Path 2:250/1@fidonet 1689335430 Fri Jul 14 12:50:30 2023 GMT
Seenby 2:25/0 25/21 1:153/757 153/7715 214/22 2:250/0 250/1 3 5 6 8 11 13 Seenby 1:261/38 2:263/0 1:317/3 2:341/66 467/4 3:712/1321 1:3634/12 2:5020/1042
Pw secret
--

There is no mention of REPLACE in the system.log or debug.log or error.log

Vincent

--- Mageia Linux v8 X64/Mbse v1.0.8.3/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Hello Sean!

Saturday July 08 2023 16:32, you wrote to me:

Vincent Coen wrote to All <=-

Problem is it is NOT doing any replacing.

That's really odd. Is the TIC file being created correctly?

I have turned OFF virus detection in that there is no program now set.

Cannot get clamav to work in stream mode and the other (standard) mode is too slow.

Can't think that that would be the reason it no longer works, though - but I could be wrong. - Been programming for too many years to start 'assuming'.

Vincent

--- Mageia Linux v8 X64/Mbse v1.0.8.3/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Vincent Coen wrote to Sean Dennis <=-

Cannot get clamav to work in stream mode and the other (standard) mode
is too slow.

Both Andrew and I have been able to get ClamAV working great with MBSE in stream mode; what was the issue?

Can't think that that would be the reason it no longer works, though -
but I could be wrong. - Been programming for too many years to start 'assuming'.

Behind every solution, there's always a bigger problem to break it...

That being said, a lot of MBSE's codebase is an absolute mess.

-- Sean

... Mary had a little RAM; only about a meg or so.
___ MultiMail/Linux v0.52

--- Maximus/2 3.01
* Origin: Outpost BBS - bbs.outpostbbs.net:10323 (1:18/200)

Vincent Coen wrote to Sean Dennis <=-

Replaces QBSHELL*.ZIP

I don't think you can use a wildcard. I believe it has to be an actual filename. I am no expert on this but many years ago I talked to the Allfix developer about this.

-- Sean

... Don't hit me, Mr. Moderator...I'll go back on topic...I swear!
___ MultiMail/Linux v0.52

--- Maximus/2 3.01
* Origin: Outpost BBS - bbs.outpostbbs.net:10323 (1:18/200)

Hello Sean!

Friday July 14 2023 16:17, you wrote to me:

Vincent Coen wrote to Sean Dennis <=-

Replaces QBSHELL*.ZIP

I don't think you can use a wildcard. I believe it has to be an
actual filename. I am no expert on this but many years ago I talked
to the Allfix developer about this.

Thanks for that and I got the same in Z2REGION25 so will remove the dups and remember to just kill off the previous one.


Vincent

--- Mageia Linux v8 X64/Mbse v1.0.8.3/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Hello Sean!

Friday July 14 2023 16:17, you wrote to me:

Vincent Coen wrote to Sean Dennis <=-

Replaces QBSHELL*.ZIP

I don't think you can use a wildcard. I believe it has to be an
actual filename. I am no expert on this but many years ago I talked
to the Allfix developer about this.

Found the TIC spec in doc FTS-5006.001 which states :

Replaces

This specifies that the file replaces one or more files that
were sent previously. It is up to the receiving system if it
honours this keyword.
The wildcard characters '?' and '*' may be used with the usual
meaning as in MS-DOS.
Some tic processors do not support wild cards and use of
wild cards with this keyword may cause unexpected results.


With the proviso of unexpected results which I assume means that if you use *.*
it will scrap the lot so any s/w must check that such a first '*' is not less than the 5 chars etc.

So the question is what does mbse do and more importantly in what program ?



Vincent

--- Mageia Linux v8 X64/Mbse v1.0.8.3/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Vincent Coen wrote to Sean Dennis <=-

Thanks for that and I got the same in Z2REGION25 so will remove the
dups and remember to just kill off the previous one.

I understand....when I do Cheepware updates, I spend a considerable amount
of time making sure I replace the right filenames.

-- Sean

... Chips have little nutritional value so you need to eat the whole bag.
___ MultiMail/Linux v0.52

--- Maximus/2 3.01
* Origin: Outpost BBS - bbs.outpostbbs.net:10323 (1:18/200)

Vincent Coen wrote to Sean Dennis <=-

So the question is what does mbse do and more importantly in what
program ?

That's best directed at Andrew.

-- Sean

... "What? This isn't the files section?"
___ MultiMail/Linux v0.52

--- Maximus/2 3.01
* Origin: Outpost BBS - bbs.outpostbbs.net:10323 (1:18/200)

Hello Vincent!

Friday July 14 2023 21:46, Vincent Coen wrote to Sean Dennis:

I don't think you can use a wildcard. I believe it has to be an
actual filename. I am no expert on this but many years ago I
talked to the Allfix developer about this.

Found the TIC spec in doc FTS-5006.001 which states :

Replaces

This specifies that the file replaces one or more files that
were sent previously. It is up to the receiving system if it
honours this keyword.
The wildcard characters '?' and '*' may be used with the usual
meaning as in MS-DOS.
Some tic processors do not support wild cards and use of
wild cards with this keyword may cause unexpected results.

With the proviso of unexpected results which I assume means that if
you use *.* it will scrap the lot so any s/w must check that such a
first '*' is not less than the 5 chars etc.

So the question is what does mbse do and more importantly in what
program ?

MBSE does NOT support wildcards in the .TIC Replaces directive. The processing of the Replaces directive is done in addbbs.c which handles adding the file to the BBS file database.

Andrew

---
* Origin: Bits & Bytes BBS * V.Everything! * 860/503-8857 (1:320/119)

Hello Andrew!

Saturday July 15 2023 23:54, you wrote to me:

Hello Vincent!

Friday July 14 2023 21:46, Vincent Coen wrote to Sean Dennis:

I don't think you can use a wildcard. I believe it has to be an
actual filename. I am no expert on this but many years ago I
talked to the Allfix developer about this.

Found the TIC spec in doc FTS-5006.001 which states :

Replaces

This specifies that the file replaces one or more files that
were sent previously. It is up to the receiving system if it
honours this keyword.
The wildcard characters '?' and '*' may be used with the
usual
meaning as in MS-DOS.
Some tic processors do not support wild cards and use of
wild cards with this keyword may cause unexpected results.

With the proviso of unexpected results which I assume means that
if you use *.* it will scrap the lot so any s/w must check that
such a first '*' is not less than the 5 chars etc.

So the question is what does mbse do and more importantly in what
program ?

MBSE does NOT support wildcards in the .TIC Replaces directive. The processing of the Replaces directive is done in addbbs.c which handles adding the file to the BBS file database.

That's a shame but I will have to live with it.
The trouble is I get new additions to one area i.e., PDNBASIC as a file
without any TIC details including description so I have to do a unzip -z filename.ZIP just to get the one liner to use when running hatch - that then gets the full description via file_id.diz but if I just use a one word detail, that get passed on to all downlinks instead.

I have now asked him to specify the previous fn.

Can I assume that if I specify old fn to REPLACE it is NOT case sensitive ?

He does NOT run a BBS.

Vincent

--- Mageia Linux v8 X64/Mbse v1.0.8.3/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)