1. MakeNL check for an existing archive and remove it prior to archiving the
segment for submission.
2. When uncompressing incoming segment archives, compare file dates on
all
files unpacked and use the most recent.
I have discovered an issue that can manifest itself when archived
segments are submitted to the next *C up the chain. When archiving
the new segment prior to submission, MakeNL doesn't check to see if
the archive already exists. The result is submission of an archive containing the new segment, as well as an older one.
There are two solutions that I've come up with:recent.
1. MakeNL check for an existing archive and remove it prior to archiving the segment for submission. 2. When uncompressing incoming segment archives, compare file dates on all files unpacked and use the most
What do you think? I'm leaning towards number 2 first, as that will help in cases where the lower level *C hasn't upgraded his version of MakeNL yet.
As a work around, the problem can be avoided by disabling the
compression of submitted segments by adding:
THReshold -1 -1
to your control file.
I have discovered an issue that can manifest itself when archived
segments are submitted to the next *C up the chain. When archiving
the new segment prior to submission, MakeNL doesn't check to see if
the archive already exists. The result is submission of an archive containing the new segment, as well as an older one.
There are two solutions that I've come up with:
1. MakeNL check for an existing archive and remove it prior to
archiving the segment for submission. 2. When uncompressing incoming segment archives, compare file dates on all files unpacked and use the most recent.
What do you think?
I'm leaning towards number 2 first, as that will help in cases where
the lower level *C hasn't upgraded his version of MakeNL yet.
Hello everybody!
I have discovered an issue that can manifest itself when archived
segments are submitted to the next *C up the chain. When archiving
the new segment prior to submission, MakeNL doesn't check to see if
the archive already exists. The result is submission of an archive containing the new segment, as well as an older one.
There are two solutions that I've come up with:
1. MakeNL check for an existing archive and remove it prior to
archiving the segment for submission. 2. When uncompressing incoming segment archives, compare file dates on all files unpacked and use the
most recent.
What do you think? I'm leaning towards number 2 first, as that will
help in cases where the lower level *C hasn't upgraded his version of
MakeNL yet.
As a work around, the problem can be avoided by disabling the
compression of submitted segments by adding:
THReshold -1 -1
to your control file.
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 906 |
Nodes: | 10 (1 / 9) |
Uptime: | 217:50:55 |
Calls: | 12,037 |
Calls today: | 2 |
Files: | 186,477 |
Messages: | 2,214,639 |