[arm-allstar] Bug fix update!

[Doug Crompton]

Dave,

 If this needs to be done at the end user level I think it could be done
but if it could be presented that way to begin with FROM the source it
would be better. All we do is present the data given to us from Allstar
like -

11:01:37.217

I am assuming that is hours:min:sec:ms  ??  We certainly don't need ms for
display purposes so it could be days:hours:min:sec . So this would be
displayed as  0:11:01:37   if it were beyond a day then

1:13:45:30

Could the source code be changed to pass the data in that way? Eliminating
the last ms? would not change the output formatting.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*


On Tue, May 23, 2017 at 10:06 AM, "David McGough via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

>
> Hi LaRoy,
>
> Yes, agreed, that would be a nice enhancement!
>
> 73, David KB4FXC
>
> On Tue, 23 May 2017, "LaRoy McCann via arm-allstar" wrote:
>
> > Doug,
> > You guys are doing some really great work.  I really appreciate it.
> >
> > I have been wondering if you could put on your todo list to display the
> > received and connected times on Allmon in a format that shows
> > days:hours:min:sec instead of just hours:min:sec.  I think that would
> > make the readability of the time values much more pleasant.
> >
> > LaRoy McCann K5TW
> >
> > On 5/22/2017 10:04 PM, "Doug Crompton via arm-allstar" wrote:
> > > Yet another, since the beginning of Allstar, problem has been fixed!
> > > Several typdef errors in the code caused the status time values to give
> > > bogus times in lsnodes, Allmon, supermon, and on the Allstar status
> server.
> > > This happened if times exceeded 956.5 hours or 24.8 days. It effected
> most
> > > of the displayed times like TX time, Connect time, kerchunks, etc.
> This has
> > > no relation to the timer accuracy update of several days ago and as
> far as
> > > we know had no operational effects other than the displayed values BUT
> it
> > > potentially could cause other issues due to memory corruption. Users
> should
> > > update at their earliest convenience.
> > >
> > > Version 1.5 users should update using item 1 in the ADMIN menu. Since
> this
> > > effects the accuracy of the times on the update server users of hamvoip
> > > code prior to version 1.5 and other code versions will still report
> bogus
> > > info to the Allstar status server in certain situations.
> > >
> > >
> > > *73 Doug*
> > >
> > > *WA3DSP*
> > >
> > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> > > _______________________________________________
> > >
> > > arm-allstar mailing list
> > > arm-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > >
> >
> >
> >
> > ---
> > This email has been checked for viruses by Avast antivirus software.
> > https://www.avast.com/antivirus
> > _______________________________________________
> >
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> >
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
>