• Truncated packets, etc.

    From Joe Delahaye@DIGDIST/BATTLEST/FREEWAY to Digital Man on Wed May 11 20:20:00 2016
    I now truncate (I think I have the right terminology) all of my outgoing mail. I am ending up with hundreds of 0 byte files in my outbound. I thought they were supposed to disappear after 24 hours? Am I missing something here?

    ---
    Synchronet The Lion's Den BBS
  • From Digital Man@DIGDIST/BATTLEST/FREEWAY to Joe Delahaye on Thu May 12 00:37:00 2016
    Re: Truncated packets, etc.
    By: Joe Delahaye to Digital Man on Wed May 11 2016 08:20 pm

    I now truncate (I think I have the right terminology) all of my outgoing mail. I am ending up with hundreds of 0 byte files in my outbound. I thought they were supposed to disappear after 24 hours? Am I missing something here?

    That's true of bundle files, but not packets. Can you give an example of the 0-byte filenames (and the corresponding date/time stamps)?

    In either case, we either have a bug to fix a feature to implement, so let me know.

    digital man

    Synchronet/BBS Terminology Definition #43:
    XPDEV = Cross-platform Development
    Norco, CA WX: 58.2F, 88.0% humidity, 3 mph SE wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Joe Delahaye@DIGDIST/BATTLEST/FREEWAY to Digital Man on Thu May 12 13:54:00 2016
    Re: Truncated packets, etc.
    By: Digital Man to Joe Delahaye on Thu May 12 2016 00:37:00

    I now truncate (I think I have the right terminology) all of my
    outgoing mail. I am ending up with hundreds of 0 byte files in my
    outbound. I thought they were supposed to disappear after 24 hours?
    Am I missing something here?

    That's true of bundle files, but not packets. Can you give an example of the 0-byte filenames (and the corresponding date/time stamps)?

    In either case, we either have a bug to fix a feature to implement, so let me know.


    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

    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.

    ** I checked this pkt, and it was created here for one of my downlinks, who get archived mail, thus a bundle. That would have been an #########.fr#

    ---
    Synchronet The Lion's Den BBS
  • From Digital Man@DIGDIST/BATTLEST/FREEWAY to Joe Delahaye on Thu May 12 14:55:00 2016
    Re: Truncated packets, etc.
    By: Joe Delahaye to Digital Man on Thu May 12 2016 01:54 pm

    Re: Truncated packets, etc.
    By: Digital Man to Joe Delahaye on Thu May 12 2016 00:37:00

    I now truncate (I think I have the right terminology) all of my
    outgoing mail. I am ending up with hundreds of 0 byte files in my
    outbound. I thought they were supposed to disappear after 24 hours?
    Am I missing something here?

    That's true of bundle files, but not packets. Can you give an example of the 0-byte filenames (and the corresponding date/time stamps)?

    In either case, we either have a bug to fix a feature to implement, so let me know.


    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

    Old 0-byte bundles are deleted when a new bundle is created with with the same 2-character day code. So those 0-byte files above would not be deleted until a new 000000005f.fr* bundle was to be created, which would not be until 5/13/2016. If you have 0-byte bundle files older 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.

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

    ** I checked this pkt, and it was created here for one of my downlinks, who get archived mail, thus a bundle. That would have been an #########.fr#

    "FR?" is an extension just for bundles created on a Friday. Anyway, let me know which directory those .pkt files are sitting in and I'll have a clue as to why they weren't bundled and deleted.

    digital man

    Synchronet "Real Fact" #15:
    Synchronet first supported FidoNet networking (with SBBSFIDO) in 1992.
    Norco, CA WX: 83.5F, 42.0% humidity, 9 mph SE wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Joe Delahaye@DIGDIST/BATTLEST/FREEWAY to Digital Man on Thu May 12 20:55:00 2016
    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

    Old 0-byte bundles are deleted when a new bundle is created with with the same 2-character day code. So those 0-byte files above would not be deleted until a new 000000005f.fr* bundle was to be created, which would not be until 5/13/2016. If you have 0-byte bundle files older 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.

    What directory are those *.pkt files in? Have you looked at the packet 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.


    ** I checked this pkt, and it was created here for one of my
    downlinks, who get archived mail, thus a bundle. That would have been
    an #########.fr#

    "FR?" is an extension just for bundles created on a Friday. Anyway, let me know which directory those .pkt files are sitting in and I'll have a clue as to why they weren't bundled and deleted.

    I understand the extension, but just used that as an example. I may have looked upt the date as the packet date, is actually a Friday All of the above
    are in the outbound directory. I can send you the full directory listing if you wish.

    ---
    Synchronet The Lion's Den BBS
  • From Digital Man@DIGDIST/BATTLEST/FREEWAY to Joe Delahaye on Fri May 13 16:05:00 2016
    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

    Old 0-byte bundles are deleted when a new bundle is created with with the same 2-character day code. So those 0-byte files above would not be deleted until a new 000000005f.fr* bundle was to be created, which would not be until 5/13/2016. If you have 0-byte bundle files older 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.

    What directory are those *.pkt files in? Have you looked at the packet 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.3F, 43.0% humidity, 15 mph SE wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Joe Delahaye@DIGDIST/BATTLEST/FREEWAY to Digital Man on Fri May 13 20:41:00 2016
    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.

    What directory are those *.pkt files in? Have you looked at the
    packet 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.

    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