I have the following in my filetoss.ini

; If this is true, then Mystic will allow the REPLACE TIC option, which will
; remove and replace files by the specified file mask.

allow_replace = true

Isn't this supposed to allow a file with same name to be overwritten, by the newer file? If so, it is not happening here. Is there something I am
missing?

Ruben Figueroa aka Zazz
Mystic Prison Board Sysop
telnet://pbmystic.rdfig.net:24
Web: www.rdfig.net

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Mystic Prison BBS*Mesquite Tx (21:1/134)

On 27 Aug 2019 at 07:00p, Zazz pondered and said...

I have the following in my filetoss.ini

; If this is true, then Mystic will allow the REPLACE TIC option, which will ; remove and replace files by the specified file mask.

allow_replace = true

Isn't this supposed to allow a file with same name to be overwritten, by the newer file? If so, it is not happening here. Is there something I
am missing?

Are you seeing files with accompanying TICs coming into your BBS that are
being sent to bad files dir as a dupes?

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)

The auto replace will work if the TIC has a REPLACE command in it.

But you also need to check how Mystic handles dupe scanning of file bases.

In the main file settings config change dupe scan from 'all' to 'current'

I expect what is happening Ruben is that you already have the incoming file
in your file bases but in another base other than the one the incoming file
is intended to land in.

So if you had a copy of the fsxNet nodelist in two file bases, a new nodelist arrived with a replace command in a TIC etc. the file would not get tossed in as Mystic (if set to 'all') would say there's a copy of the fsxNet nodelist
in file base ABC already so I won't toss it into file base DEF like you're asking me to.

Changing that setting to 'current' will negate that issue.

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I have the following in my filetoss.ini

; If this is true, then Mystic will allow the REPLACE TIC option, whi will ; remove and replace files by the specified file mask.

allow_replace = true

Isn't this supposed to allow a file with same name to be overwritten, the newer file? If so, it is not happening here. Is there something am missing?

Are you seeing files with accompanying TICs coming into your BBS that are being sent to bad files dir as a dupes?

Yes, tic file is present and the tic file is sent to the bad files dir as
dupes

The auto replace will work if the TIC has a REPLACE command in it.

But you also need to check how Mystic handles dupe scanning of file
bases.

In the main file settings config change dupe scan from 'all' to 'current'

I expect what is happening Ruben is that you already have the incoming file in your file bases but in another base other than the one the incoming file is intended to land in.

I did change that to Current, it was set to None

Ruben Figueroa aka Zazz
Mystic Prison Board Sysop
telnet://pbmystic.rdfig.net:24
Web: www.rdfig.net

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Mystic Prison BBS*Mesquite Tx (21:1/134)