Hello All!

Have now received new nodelists and nodedifs files the REPLACE is now working correctly.

It is a bug that if a file comes in for tic processing that has a REPLACE keyword without any files matching the keyword then mbse will delete the incoming file after processing (i.e., downlinks and any magic processing.

Vincent

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

Hello Vincent,

It is a bug that if a file comes in for tic processing that has a
REPLACE keyword without any files matching the keyword then mbse will delete the incoming file after processing (i.e., downlinks and any
magic processing.

I don't think it is generally. I have a point that was down for a time and each week there was a new nodelist that replaced the old one and MBSE removed undelivered tics that were associated with replaced nodelists for that point.

That's a good thing at least in this case.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Alan!

Friday November 20 2020 17:17, you wrote to me:

Hello Vincent,

It is a bug that if a file comes in for tic processing that has a
REPLACE keyword without any files matching the keyword then mbse
will delete the incoming file after processing (i.e., downlinks
and any magic processing.

I don't think it is generally. I have a point that was down for a time
and each week there was a new nodelist that replaced the old one and
MBSE removed undelivered tics that were associated with replaced
nodelists for that point.

That's a good thing at least in this case.

Quite, but the scenario I mentioned is a more important problem but in a limited manner.

The solution is simple if it applies to any one by going to the correct file directory (bbs) running touch on an old file name.extention i.e., touch nodelist.z11

Then import it in to the system for the specific file area.

Then double check that the file files.bbs is created or updated with the file added.


Just a pain to remember.


Vincent

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

Hello Vincent,

That's a good thing at least in this case.

Quite, but the scenario I mentioned is a more important problem but in
a limited manner.

I haven't noticed issues when replacing files but maybe I just didn't see it.

The solution is simple if it applies to any one by going to the
correct file directory (bbs) running touch on an old file
name.extention i.e., touch nodelist.z11

Yes, the file to be replaced should be removed from the FDB, files.bbs, magics and deleted, both the file and the symlink.

Then import it in to the system for the specific file area.

Then double check that the file files.bbs is created or updated with
the file added.

Yes, is the new file not added to to FDB, files.bbs and magics?

Just a pain to remember.

Which step is not happening the way it needs too?

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Alan!

Saturday November 21 2020 11:48, you wrote to me:

Hello Vincent,

That's a good thing at least in this case.

Quite, but the scenario I mentioned is a more important problem
but in a limited manner.

I haven't noticed issues when replacing files but maybe I just didn't
see it.

The solution is simple if it applies to any one by going to the
correct file directory (bbs) running touch on an old file
name.extention i.e., touch nodelist.z11

Yes, the file to be replaced should be removed from the FDB,
files.bbs, magics and deleted, both the file and the symlink.

Then import it in to the system for the specific file area.

Then double check that the file files.bbs is created or updated
with the file added.

Yes, is the new file not added to to FDB, files.bbs and magics?

Just a pain to remember.

Which step is not happening the way it needs too?

IF, the replacing file does NOT exist then after all primary processing the incoming file is deleted.

You may well not want this :)

Vincent

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

Hello Vincent,

IF, the replacing file does NOT exist then after all primary
processing the incoming file is deleted.

I have not seen this but it could be my attention was elsewhere.

You may well not want this :)

No, we don't want this to happen. If that is happening we'll need one of the coders to have a look.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Alan!

Sunday November 22 2020 20:35, you wrote to me:

Hello Vincent,

IF, the replacing file does NOT exist then after all primary
processing the incoming file is deleted.

I have not seen this but it could be my attention was elsewhere.

You may well not want this :)

No, we don't want this to happen. If that is happening we'll need one
of the coders to have a look.

Or even one of the programmers.

A coder codes from a very detailed program specification where all the T's are crossed and the i's are dotted.

Not the same thing.


Vincent

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

Hello Vincent,

No, we don't want this to happen. If that is happening we'll need
one of the coders to have a look.

Or even one of the programmers.

A coder codes from a very detailed program specification where all the
T's are crossed and the i's are dotted.

Not the same thing.

I think Andrew or Sean could look in on it and make any needed changes.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)