Subj : Truncated packets, etc.
To   : Digital Man
From : Joe Delahaye
Date : Fri May 13 2016 20:41:00

  Re: Truncated packets, etc.
  By: Digital Man to Joe Delahaye on Fri May 13 2016 16:05:44

 > >>> 04/01/2016  09:23            14,166 01092348.pkt **
 > >>> 04/01/2016  09:28               963 01092849.pkt
 > >>> 04/01/2016  09:43               929 01094350.pkt
 > >>> 04/01/2016  09:43               929 01094351.pkt
 > >>> 04/01/2016  09:48               534 01094851.pkt
 > >>> 04/01/2016  09:48               534 01094852.pkt
 > >>> 04/01/2016  09:58             1,391 01095853.pkt
 > >>> 04/01/2016  09:58             1,391 01095854.pkt

 > >>> These normally get added to  a bundle and deleted I would think.

 > DM>> What directory are those *.pkt files in? Have you looked at the
 > DM>> packet headers (e.g. with pktdump.exe) to see who they are
 > DM>> addressed to?

 >> Outbound.  I checked the one packet marked with ** as noted below.  It
 >> was for one of my downlinks here in my net.  I'll check a little
 >> further and see what the log file for that date has to say.

 DM> Looking at those packet filenames, I can tell they were created with
 DM> SBBSecho v2. It's possible that node was configured for uncompressed
 DM> packets at that time? Does the FLO file for that node point to these
 DM> packets? If not, they're just orphans and should either be deleted, or if
 DM> you move them to your SBBSecho temp directory, SBBSecho v3 should find
 DM> them and bundle and attach them as appropriate.

Ok, moving those prior to May, to the temp directory.  I'll see what happens
and let you know

---
 þ Synchronet þ The Lion's Den BBS

.