I just dug up an old packet I had laying around here and tried pktdate on it:

bbs@filegate:~/pktdate$ ./pktdate -me -c 1a35fac1.pkt Pktdate Rev. 1.5: processing 1a35fac1.pkt (type: 2+) Packet header date (D/M/Y): 19.9.2012 fixed to 25.3.2016. Packet sender: 1:261/38.0
Msg #001: Date "19 Sep 12 15:50:00" fixed to "25 Mar 16 16:38:51" (rc 8). Msg
#001: Message sender is "Nick Kill@1:261/38". Msg #002: Date "19 Sep 12 15:54:22" fixed to "25 Mar 16 16:38:51" (rc 8). Msg #002: Message sender is "Janis Kracht@1:261/38". Wrote changes to 1a35fac1.pkt.

Interesting.. :)

Take care,
Janis

--- BBBS/Li6 v4.10 Dada-2
* Origin: Prism bbs (1:261/38)

25 Mar 16 16:47, you wrote to Vince Coen:

I just dug up an old packet I had laying around here and tried pktdate on it:

bbs@filegate:~/pktdate$ ./pktdate -me -c 1a35fac1.pkt Pktdate Rev. 1.5: processing 1a35fac1.pkt (type: 2+) Packet header date (D/M/Y): 19.9.2012 fixed to 25.3.2016. Packet sender: 1:261/38.0 Msg #001: Date "19 Sep 12 15:50:00" fixed to "25 Mar 16 16:38:51" (rc 8). Msg #001: Message sender is "Nick Kill@1:261/38". Msg #002: Date "19 Sep 12 15:54:22" fixed to "25 Mar 16 16:38:51" (rc 8). Msg #002: Message sender is "Janis Kracht@1:261/38". Wrote changes to 1a35fac1.pkt.

Interesting.. :)

yup... i've been running it here since it was first every released... have updated through each version... have just seen that #6 was released but haven't
yet updated to it... i stopped changing the dates in the packets after the last
round of regurges... as you can see in your output, the date was too old so pktdate fixed it to today's date... that may cause other systems to not catch the post as a dupe if their dupe database goes back that far...

anyway, here's what i currently use...


rem set pdate=pktdate -k -c -l2 -S -L%fd%\pktd-sec.log
rem ***
rem *** -c means to correct the pkt... stopped correcting on 7 Jul 2014
rem *** -k means to keep the original pkt if we correct any dates in it
rem *** -p means "past" and "9y" means "9+ years"
rem *** -f means "future" and "1m" means "1+ month"
rem *** -l is the logging level
rem *** -S changes seadog dates to standard ftsc dates
rem *** -L is the log file name
set pdate=pktdate -k -p9y -f1m -l2 -S -L%fd%\pktd-sec.log
gosub do_mydate
echo %MYDATE% [723] %pdate% | %SLOGS%
for %%i in ( *.pkt) do %pdate% %%i


i set my command in an environment variable so i can echo it to my processing log... then i just toss it at each pkt in my secure and insecure directories...
each has its own log... in the above, if the date is older than 9 years or newer than 1 month in the future then we note it in the processing log... if i was using "-c" it would be corrected in the pkt... i also have it changing the seadog date format to the fido date format since all my software expects the fido format...


)\/(ark

Always Mount a Scratch Monkey

... Bart's Blackboard: "The cafeteria deep fryer is not a toy."
---
* Origin: (1:3634/12.73)

Hello Janis!

Friday March 25 2016 16:47, you wrote to me:

Does that mean it worked ?

Just wondering as the original date looks ok to me e.g., 19/09/2012 !

.. no have not checked what the '-me' means yet :)

I just dug up an old packet I had laying around here and tried pktdate
on it:

bbs@filegate:~/pktdate$ ./pktdate -me -c 1a35fac1.pkt Pktdate Rev.
1.5: processing 1a35fac1.pkt (type: 2+) Packet header date (D/M/Y): 19.9.2012 fixed to 25.3.2016. Packet sender: 1:261/38.0 Msg #001: Date
"19 Sep 12 15:50:00" fixed to "25 Mar 16 16:38:51" (rc 8). Msg #001: Message sender is "Nick Kill@1:261/38". Msg #002: Date "19 Sep 12
15:54:22" fixed to "25 Mar 16 16:38:51" (rc 8). Msg #002: Message
sender is "Janis Kracht@1:261/38". Wrote changes to 1a35fac1.pkt.

Interesting.. :)

Take care,
Janis

Vince

--- Mageia Linux v5/Mbse v1.0.6/GoldED+/LNX 1.1.501-b20150715
* Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)

Hello Janis!

Friday March 25 2016 16:47, you wrote to me:

I have set it to run under mbse although similar processing is already within mbse mail tossing..

Will be interesting to see what happens?


Vince

bbs@filegate:~/pktdate$ ./pktdate -me -c 1a35fac1.pkt Pktdate Rev.
1.5: processing 1a35fac1.pkt (type: 2+) Packet header date (D/M/Y): 19.9.2012 fixed to 25.3.2016. Packet sender: 1:261/38.0 Msg #001: Date
"19 Sep 12 15:50:00" fixed to "25 Mar 16 16:38:51" (rc 8). Msg #001: Message sender is "Nick Kill@1:261/38". Msg #002: Date "19 Sep 12
15:54:22" fixed to "25 Mar 16 16:38:51" (rc 8). Msg #002: Message
sender is "Janis Kracht@1:261/38". Wrote changes to 1a35fac1.pkt.

Interesting.. :)

Take care,
Janis

Vince

--- Mageia Linux v5/Mbse v1.0.6/GoldED+/LNX 1.1.501-b20150715
* Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)

Hi Mark,

I just dug up an old packet I had laying around here and tried pktdate on
it:

bbs@filegate:~/pktdate$ ./pktdate -me -c 1a35fac1.pkt Pktdate Rev. 1.5:
processing 1a35fac1.pkt (type: 2+) Packet header date (D/M/Y): 19.9.2012
fixed to 25.3.2016. Packet sender: 1:261/38.0 Msg #001: Date "19 Sep 12
15:50:00" fixed to "25 Mar 16 16:38:51" (rc 8). Msg #001: Message sender
is "Nick Kill@1:261/38". Msg #002: Date "19 Sep 12 15:54:22" fixed to "25 >> Mar 16 16:38:51" (rc 8). Msg #002: Message sender is "Janis
Kracht@1:261/38". Wrote changes to 1a35fac1.pkt.

Interesting.. :)

yup... i've been running it here since it was first every released... have

I used to run it way back.. then never noticed the source until Ben sent it out

pktdate fixed it to today's date... that may cause other systems to not catch the post as a dupe if their dupe database goes back that far...

Sure.. like I said this was just an old packet I had kept for some reason or other.. so it was a good test pkt for this.. (i.e., not a live packet in the stream).

anyway, here's what i currently use...

rem set pdate=pktdate -k -c -l2 -S -L%fd%\pktd-sec.log
rem ***
rem *** -c means to correct the pkt... stopped correcting on 7 Jul 2014
rem *** -k means to keep the original pkt if we correct any dates in it
rem *** -p means "past" and "9y" means "9+ years"
rem *** -f means "future" and "1m" means "1+ month"
rem *** -l is the logging level
rem *** -S changes seadog dates to standard ftsc dates
rem *** -L is the log file name
set pdate=pktdate -k -p9y -f1m -l2 -S -L%fd%\pktd-sec.log
gosub do_mydate
echo %MYDATE% [723] %pdate% | %SLOGS%
for %%i in ( *.pkt) do %pdate% %%i

Looks good..

i set my command in an environment variable so i can echo it to my processing
log... then i just toss it at each pkt in my secure and insecure directories..
each has its own log... in the above, if the date is older than 9 years or
newer than 1 month in the future then we note it in the processing log... if i >was using "-c" it would be corrected in the pkt... i also have it changing the
seadog date format to the fido date format since all my software expects the fido format...

Also makes sense :)

Take care,
Janis

--- BBBS/Li6 v4.10 Dada-2
* Origin: Prism bbs (1:261/38)

Hi Vince,

Does that mean it worked ?

Just wondering as the original date looks ok to me e.g., 19/09/2012 !

This was just a packet I had somewhere over here not a live packet that I cared
to toss into Fidonet.. Just to test that the binary was going to do what I expected.. and it did :) There was nothing wrong with the date of the original
packet, it was from a long time ago..

.. no have not checked what the '-me' means yet :)

It's for "Messages English"

If you do have a file a.out, rename it to pktdate then just run pkdate with no other parameters and you'll get the help screen.

BTW, I did rename the uppercase file PKTDATE.C to lower case, and since the source #includes pktdate.lng (lower case) that's when I actually got it to compile correctly.

Take care,
Janis

--- BBBS/Li6 v4.10 Dada-2
* Origin: Prism bbs (1:261/38)

Hello Janis!

Friday March 25 2016 20:09, you wrote to me:

Sounds like you and Mark have a later version of pktdate along with the sources.

Not the easiest to see as there is no notes/comments within the code to indicate any changes/updates.

If you or Mark does have an updated version than that issued in the Wildcat file area, I would appreciate it if you can send me the source code so I can compile it here.

As it seems to change old dates - I will attempt to modify that function (subject to a switch) so that they are ignored and that way the tosser can just
reject them if so set.

In my system I do that if msgs are 30+ days prior to current date.

If nothing else it cuts down on msgs going into the dups database for no good reason and no not that my system is loaded what with 8 cores to handle allthe workload I have never seen it up to 5% loading unless I am doing large compiles
where I have specified 3+ cores to be used ( -J5 etc).

I used the wildcat version to compile having made all filenames lower case. Linux treats the same file name but in different cases as not the same as against DOS. Windows as far as I know can also do this but not sure if it is default behaviour (at least under Win 7 Ultimate - I have not upgraded to W10 as I suspect many of my h/w drivers are not available in W10 as h/w is no longer supported on some of the kit).



Vince

Hi Vince,

Does that mean it worked ?

Just wondering as the original date looks ok to me e.g., 19/09/2012
!

This was just a packet I had somewhere over here not a live packet
that I cared to toss into Fidonet.. Just to test that the binary was
going to do what I expected.. and it did :) There was nothing wrong
with the date of the original packet, it was from a long time ago..

.. no have not checked what the '-me' means yet :)

It's for "Messages English"

If you do have a file a.out, rename it to pktdate then just run pkdate
with no other parameters and you'll get the help screen.

BTW, I did rename the uppercase file PKTDATE.C to lower case, and
since the source #includes pktdate.lng (lower case) that's when I
actually got it to compile correctly.

--- Mageia Linux v5/Mbse v1.0.6/GoldED+/LNX 1.1.501-b20150715
* Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)

28 Mar 16 13:30, you wrote to Janis Kracht:

Sounds like you and Mark have a later version of pktdate along with
the sources.

i don't know if i have the sources or not... i'm using what was released in Y2KTOOL5.ZIP in the COORDUTL file distribution area... that's the same area that the new makenl releases have been being posted to... it is also the same area where the 32bit remake of daynbr was hatched as well as the distribution of the errflags program and numerous other tools that FTN coordinators would be
interested in...

)\/(ark

Always Mount a Scratch Monkey

... I'm not stupid, I'm not expendable, and I'm not going!
---
* Origin: (1:3634/12.73)

Hi Vince,

Friday March 25 2016 20:09, you wrote to me:

Sounds like you and Mark have a later version of pktdate along with the sources.

I'll send you the file that just came through wcf FDN's file echo wcf_4utl.. that file is named PKTDATE.ZIP

If you or Mark does have an updated version than that issued in the Wildcat file area, I would appreciate it if you can send me the source code so I can compile it here.

Sure thing..

Take care,
Janis

--- BBBS/Li6 v4.10 Dada-2
* Origin: Prism bbs (1:261/38)

Hello mark!

Monday March 28 2016 10:57, you wrote to me:

28 Mar 16 13:30, you wrote to Janis Kracht:

Sounds like you and Mark have a later version of pktdate along
with the sources.

i don't know if i have the sources or not... i'm using what was
released in Y2KTOOL5.ZIP in the COORDUTL file distribution area...
that's the same area that the new makenl releases have been being
posted to... it is also the same area where the 32bit remake of daynbr
was hatched as well as the distribution of the errflags program and
numerous other tools that FTN coordinators would be interested in...

Must have another look for those on my system.

If I start it after dinner might get a result tomorrow.
Draw back of having large dasd storage here.


Vince

--- Mageia Linux v5/Mbse v1.0.6/GoldED+/LNX 1.1.501-b20150715
* Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)

Hello mark!

Monday March 28 2016 10:57, you wrote to me:

i don't know if i have the sources or not... i'm using what was
released in Y2KTOOL5.ZIP in the COORDUTL file distribution area...
that's the same area that the new makenl releases have been being
posted to... it is also the same area where the 32bit remake of daynbr
was hatched as well as the distribution of the errflags program and
numerous other tools that FTN coordinators would be interested in...

Follow up from prev. msg - nope I do not seem to have that area or more importantly that file.

Must have been lost a few years back when I could not recover 2 odd gigs of dasd from a back up.

Must remember to have a look on Janis's system.


Vince

--- Mageia Linux v5/Mbse v1.0.6/GoldED+/LNX 1.1.501-b20150715
* Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)

Hi Vince,

Follow up from prev. msg - nope I do not seem to have that area or more importantly that file.

Must have been lost a few years back when I could not recover 2 odd gigs of dasd from a back up.

Ah, I can understand that.

Must remember to have a look on Janis's system.

Y2KTOOL5.ZIP is the file in coordutil that you want for the original pktdate.

http://www.filegate.net/coordutl/Y2KTOOL5.ZIP


The pkdate.zip file that Ben sent out compiled fine for me once I renamed the .C file and .LNG file to lower case... after I did that, there were still a few
warnings, but nothing of consequence.

Take care,
Janis

--- BBBS/Li6 v4.10 Dada-2
* Origin: Prism bbs (1:261/38)