<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial, helvetica, sans-serif;font-size:12pt"><DIV>Skip,</DIV>
<DIV>Thanks for confirming what I and others have seen. As for the differing digit counts in our respective BC interval counters- I typed mine from memory (since I was on a different machine) so I'm sure the value you recorded is better :-)</DIV>
<DIV> </DIV>
<DIV>That's interesting about the 25 day rollover period. It's also the result when you decrement a 32 bit unsigned integer set to zero. </DIV>
<DIV> </DIV>
<DIV>Maiko, please let us know if there is some way we can assist in this debug effort.</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV> </DIV>
<DIV>FiSH, K6FSH<BR></DIV>
<DIV style="FONT-FAMILY: arial, helvetica, sans-serif; FONT-SIZE: 12pt"><BR>
<DIV style="FONT-FAMILY: lucida console, sans-serif; FONT-SIZE: 10pt"><FONT size=2 face=Tahoma>
<HR SIZE=1>
<B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> George [ham] VerDuin <k8rra@ameritech.net><BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> nos-bbs@tapr.org<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Sat, July 31, 2010 8:35:50 PM<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [nos-bbs] Potential Timer Issue in JNOS (3rd try- sorry)<BR></FONT><BR>Interesting Bob...<BR><BR><BR>On 07/28/2010 12:39 PM, fish810 wrote:<BR>> >>SNIP<<<BR>> <BR>> <BR>> AX25 BCINTERVAL<BR>> Broadcast timer 403528419/1800<BR>> <BR>At K8RRA the BC ceased after July 26 07:54:45.<BR>Jnos was booted 30days +8hrs ago<BR>That's about 25days [more detail later].<BR>So I can confirm your issue here on a F-11 OS & jnos2.0f<BR>Here is my console [quoted]:<BR>> <BR>> jnos> expire<BR>> timer: 0/0 hrs<BR>> jnos> ax25 bcinterval<BR>> Broadcast timer 4294486670/3601 seconds<BR>>
jnos> ax25 bcinterval<BR>> Broadcast timer 4294483855/3601 seconds<BR>> jnos> <BR>From it you see:<BR> 1) I am not using the EXPIRE feature<BR> 2) BC-interval is munged up like yours<BR> 3) BC-timer is still decrementing per normal [it's just going to be a 25-day wait]<BR><BR>You and I have a different digit count in our email timer value:<BR>yours is 4.03X10^8<BR>mine is 4.29X10^9<BR>It probably won't change the solution...<BR><BR>What is most interesting is this:<BR>A timer accurate to 1ms rolls over a 32bit binary integer at about 25days.<BR>The timer runs out of bits...[if my conversion is accurate]<BR>KEWL<BR>Or as Maiko put it a few hrs ago -- a pain.<BR><BR>If we were running a 64bit computer, neither of us will live long enough to see the roll-over...<BR>Isn't that a wonderful trap for future program users/debuggers?<BR><BR>So the work-around really is to reboot or otherwise reset timers prior to
25days.<BR>For long-running sites, maybe the AT command could be useful but I haven't tested it...<BR><BR>> >>SNIP<< or ideas you may have.<BR>> <BR>I hope you have used an active sense of humor...:-)<BR><BR>> Cheers,<BR>> FiSH, K6FSH<BR>> Bob Fishman<BR>> <BR>Cheers & 73<BR>Skip<BR><BR>_______________________________________________<BR>nos-bbs mailing list<BR><A href="mailto:nos-bbs@tapr.org" ymailto="mailto:nos-bbs@tapr.org">nos-bbs@tapr.org</A><BR><A href="https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs" target=_blank>https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs</A><BR></DIV></DIV></div><br>
</body></html>