[Dxspider-support] More Msg Madness
Dave Hawes
dave.n3rd at comcast.net
Thu Nov 7 12:44:43 GMT 2002
Running Build 57.146 on Win98SE
Summary:
Most recent new message is number 1, instead of the next message
in the directory sequence.
W3FRC (Spider) is connected to K2UT (Spider) and N3RS (AK1A). A
message "passing through" W3FRC from K2UT to N3RS for some
reason was assigned message number 1. It should have been
message number 20.
Here is a clip from the debug file where the message number is
assigned for the incoming message from node K2UT:
<- I K2UT PC28^W3FRC^K2UT^AA1K^W3BGN^ 7-Nov-
2002^1139Z^1^SR^ ^5^0^ ^K3WW^~
msgno 1 allocated for K2UT
new message from W3BGN to AA1K 'SR' stream K2UT/1
The PC28 is all one line.
In spider\msg there are two other files of interest:
"msgno" and "k2ut"
the contents of each is the integer 1. Both have the same file
modification date/time, that being the same as Message 1. I
remember looking at the "msgno" file last evening and it contained the
number of the last message in the directory. The question is, "Why
did the message numbering system spontaneously restart at 1?" and
further "How do the 'msgno' files and '<node call>' files interact, and
should there even be a '<node call>' file in spider\msg?"
The weirdness continues. I virtually certain at this point that if I restart
the Spider software that the message directory would be purged, and
we'd be back to square one. This has happened often recently, which
is why there are so few messages in the system.
Any info on this would be appreciated.
73 - Dave N3RD
More information about the Dxspider-support
mailing list