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

  Re: Truncated packets, etc.
  By: Joe Delahaye to Digital Man on Thu May 12 2016 08:55 pm

 >   Re: Truncated packets, etc.
 >   By: Digital Man to Joe Delahaye on Thu May 12 2016 14:55:28
 >
 >  >> Since I go thru the directory once in a while and remove, I thinks
 >  >> these are the earliest examples.
 >
 >  >> 05/06/2016  00:01                 0 0000005f.FR0
 >  >> 05/06/2016  00:02                 0 0000005f.FR1
 >  >> 05/06/2016  00:07                 0 0000005f.FR2
 >  >> 05/06/2016  00:12                 0 0000005f.FR3
 >  >> 05/06/2016  01:03                 0 0000005f.FR4
 >
 >  DM> Old 0-byte bundles are deleted when a new bundle is created with with
 >  DM> the same 2-character day code. So those 0-byte files above would not be
 >  DM> deleted until a new 000000005f.fr* bundle was to be created, which
 >  DM> would not be until 5/13/2016. If you have 0-byte bundle files older
 >  DM> than a week old, let me know.
 >
 >  >> I am also getting stuff like this though.
 >
 >  >> 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 packet
 >  DM> headers (e.g. with pktdump.exe) to see who they are 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.

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

                                            digital man

Synchronet "Real Fact" #29:
The COM I/O routines for Synchronet for DOS were written in ASM by Steve Deppe.
Norco, CA WX: 80.3øF, 43.0% humidity, 15 mph SE wind, 0.00 inches rain/24hrs

---
 þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

.