| |
VK2ZRG > TPK 17.04.04 11:55l 56 Lines 2516 Bytes #999 (0) @ WW
BID : 527_VK2ZRG
Read: GUEST
Subj: Overwrite problem. Reason found
Path: DB0FHN<DB0FOR<DB0MRW<DB0WUE<DK0WUE<DB0RES<ON0AR<IK1ZNW<ZL2TZE<VK3TE<
VK6ISP<VK2BNR<VK2TGB
Sent: 040417/0833Z @:VK2TGB.#SYD.NSW.AUS.OC #:53269 [Valley Heights] FBB7.00g
From: VK2ZRG@VK2TGB.#SYD.NSW.AUS.OC
To : TPK@WW
VK2ZRG/TPK 1.83d Msg #:527 Date:17-04-04 Time:8:37Z
Hello all TPK users,
Recently I put out two bulletins about an overwrite
problem that I was having with my private mail list. The problem was that if
I shut down TPK when there was a message header for a waiting download in my
private mail list, then the new message would overwrite the last message
when it was downloaded in the next session of TPK.
I have now found the reason why this happens. There is a flaw in the logic
of TPK when it comes to dealing with these two lines that I had in my
CONFIG.TPK file.
BR MSG_PRIV E DAYS 10
BR MSG_PRIV E K
When these lines are used, TPK will read through the MSG_PRIV.LST file and
remove old headers for the line ending in DAYS n. For the line ending in K it
will remove headers for files that have been deleted.
For the private message list, TPK will calculate the second number in the
MSG_PRIV.NUM file as the difference between the first number in MSG_PRIV.NUM
file and the number of headers in the MSG_PRIV.LST file. This happens when TPK
is started or re-initialised by entering INIT. The first number in MSG_PRIV.NUM
only gets updated when the new message is down loaded (or if you generate a
new forward message).
Most times this works OK, BUT if there is a header in MSG_PRIV.LST for an
incoming message at the BBS (but not yet down loaded) when TPK is closed down,
TPK will REDUCE the second number by one (1) when it's restarted or
initialised because of the new header.
The logic flaw is that the header for the yet to be downloaded message
should NOT be counted, but it IS.
TPK uses the second number in MSG_PRIV.NUM to calculate the message number
(file name) for a new private message download. TPK adds this second number to
an index number in RXMSG.TPK, (which was calculated previously with the higher
number) to get the new message number. This will result in a number equal to
the number of the last existing message in your MSG_PRIV directory.
The result is that the new message will overwrite the previous last message
in the MSG_PRIV directory. You will have two headers in the .LST file with
the same number but different titles etc. Both will access the same file, the
last down loaded one.
If the two BR MSG_PRIV lines are removed from CONFIG.TPK the problem does
not occur.
The problem does not affect BBSname message lists or files.
73s from Ralph VK2ZRG@VK2TGB.#SYD.NSW.AUS.OC
/ack
Read previous mail | Read next mail
| |
