I need some thoughts in what to do to remove old nodelists hatched into ~some~ msg networks that dont remove their old lists. Im having problems with one network because they do not remove/replace their old nodelist files so some of the new files are considered dupes. EXAMPLE NODEDIFF.Z24 for day 124 matches NODEDIFF.Z24 for day 224. Mystic thinks they are dupes because the filenames are the same and its tossing them to the badfiles directory.

Thanks in advance!

.\\ichael Batts
a.k.a. stizzed (because, why not?)
SysOp, The ROCK BBS III

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: The ROCK BBS III - therockbbs.net - TELNET:10023 (21:4/156)

On 03 May 2020 at 01:50a, stizzed pondered and said...

~some~ msg networks that dont remove their old lists. Im having
problems with one network because they do not remove/replace their old nodelist files so some of the new files are considered dupes. EXAMPLE NODEDIFF.Z24 for day 124 matches NODEDIFF.Z24 for day 224. Mystic
thinks they are dupes because the filenames are the same and its tossing them to the badfiles directory.

Thanks in advance!

You could look to change the dupe scan settings in mystic -cfg as a work around. I wonder what do you have your systems set to?

It sounds like the issue is the same file name already exists in another
file base?

If this is the reason for a failed import you could change Upload Dupe Sacen
in File Base Settings to 'Current'

Reshow File Header │ No
Upload Dupe Scan │ Current

--- Mystic BBS v1.12 A46 2020/04/20 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Thanks for the reply Avon!

It sounds like the issue is the same file name already exists in another file base?

I don't believe this to be the case. I checked and the same filename already exists in the file area listed in the .tic file. Again; it appears as
though nodelist files can come in with the same filenames yet can be different files. I used an example in the original message where the existing filename was NODELIST.Z24 (a nodelist for day 124) and a new (different) file named NODELIST.Z24 which is for day 224. It appears that Mystic is seeing this as the same file even though the content is different.

If this is the reason for a failed import you could change Upload Dupe Sacen in File Base Settings to 'Current'

I checked my settings and they were set as you suggested. It would be great
if there were a way to force replacement of files with the same name or turn off dupe scanning by file area.

Im now at a loss as to how to handle the nodelists that come in as dupes.

.\\ichael Batts
a.k.a. stizzed (because, why not?)
SysOp, The ROCK BBS III

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: The ROCK BBS III - therockbbs.net - TELNET:10023 (21:4/156)

On 03 May 2020, stizzed said the following...

I don't believe this to be the case. I checked and the same filename already exists in the file area listed in the .tic file. Again; it appears as though nodelist files can come in with the same filenames yet can be different files. I used an example in the original message where the existing filename was NODELIST.Z24 (a nodelist for day 124) and a
new (different) file named NODELIST.Z24 which is for day 224. It
appears that Mystic is seeing this as the same file even though the content is different.

I can think of a couple of ideas. First, you could set the age of the files
in that area to something low, such as 30 days. Mystic could remove the older ones before there are any issues.

Another idea, I haven't done anything like this yet but, write a script that would move the older files into another file area. That way you could keep
the older files, if you'd like, and only have the newest ones available in
that file echo.


---

Black Panther(RCS)
Castle Rock BBS

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

I can think of a couple of ideas. First, you could set the age of the files in that area to something low, such as 30 days. Mystic could
remove the older ones before there are any issues.

That is actually a perfectly simple solution! These files are hatched into a specific nodelist and network description/application file area and are actually hatched daily (nodelists) and monthly (desc/app) so that every 99
days the nodelist filenames match. Ill set the expiry for 90 days and just keep the last 3 months of files. WORKS FOR ME!

Thanks!!!

.\\ichael Batts
a.k.a. stizzed (because, why not?)
SysOp, The ROCK BBS III

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: The ROCK BBS III - therockbbs.net - TELNET:10023 (21:4/156)

On 03 May 2020, stizzed said the following...

That is actually a perfectly simple solution! These files are hatched into a specific nodelist and network description/application file area
and are actually hatched daily (nodelists) and monthly (desc/app) so
that every 99 days the nodelist filenames match. Ill set the expiry for 90 days and just keep the last 3 months of files. WORKS FOR ME!

That's what I ended up doing here. The reason I mentioned the other option,
was some people like to keep all of the nodelists for historical purposes.
I'm not one of them. :)

I'm glad it worked for you.


---

Black Panther(RCS)
Castle Rock BBS

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

On 03 May 2020 at 02:41p, stizzed pondered and said...

appears as though nodelist files can come in with the same filenames yet can be different files. I used an example in the original message where the existing filename was NODELIST.Z24 (a nodelist for day 124) and a
new (different) file named NODELIST.Z24 which is for day 224. It
appears that Mystic is seeing this as the same file even though the content is different.

I guess it depends on the name of the file being presented in the TIC and
it's file size, crc etc. That's what Mystic will be looking at. Hmmm.

I checked my settings and they were set as you suggested. It would be great if there were a way to force replacement of files with the same
name or turn off dupe scanning by file area.

Dupe checking is an all of BBS setting, perhaps a per base setting would be
an idea but I lean towards the former still.

So the error message in your mutil.txt logs is definitely related to dupes?

Can you post the logging?

--- Mystic BBS v1.12 A46 2020/04/20 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Thanks Avon!

So the error message in your mutil.txt logs is definitely related to dupes?

Can you post the logging?

Ill check and post when Im able.

.\\ichael Batts
a.k.a. stizzed (because, why not?)
SysOp, The ROCK BBS III

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: The ROCK BBS III - therockbbs.net - TELNET:10023 (21:4/156)