[App_rpt-users] Beagle bone black and timedatectl

Geoff ars.w5omr at gmail.com
Fri Oct 31 09:39:32 EDT 2014


On 10/27/2014 03:24 PM, Mike Lussier wrote:
> Good afternoon to all.
> I have posted on this issue before. I have and off site repeater with
> no internet access atleast until spring time, Hopefully...
> My allstar node time is way off. so I try to correct it. The outcome
> is a lock up condition. The repeater no longer responses. The only fix
> appears to be a reboot. This only brings me back to square one. The
> time is way off again.
>
> Is there something else to do once I reset the time short of a reboot
> to bring the system up on line ? is there a way to reset the system
> and use the new time stamp ?
>
> Seriously contemplating an NTP server at the site. I just don’t have
> the time to put into one right now.  
>
> I have the new 1.2 code. I'm not ready to deploy this to either of the
> repeaters just yet.
>
> command issued this morning that caused the trouble.
>
> tmedatectl " 2014-10-27 11:35:00"
>
>

I'm not sure if ntpdate is included in the BBB image or not, but that
could be added to the startup script, before asterisk is called.

manually, you could, from a command line prompt, type

astdn.sh [Enter]

then

ntpdate pool.ntp.org

then astup.sh

You could also create an 'alias', with the above information and call it
'timestamp' or something that's not a unix command.

73 = Best Regards,
-Geoff/W5OMR



More information about the App_rpt-users mailing list