odw199 wrote:
> The ntp requirement came from one instance when my pi booted up with the
> date set to 1st Jan (presumably 1972 - I didn't check). It had been
> unpowered for a while so sensible to assume the clock had reset. This
> prevented openvpn from connecting as it saw the certificates as not yet
> being valid.
>
> Could user command 1 execute before the built in time sync?
The [Boot] page shows the order that processes are run. So User commands
(in do_rebootstuff.sh) are run after settime/getTime. But I just
realised, the response from crond showing the time has been set comes up
10 or 15 seconds after the "Setup piCorePlayer complete".
I do see on the odd occasion the time displayed on the web interface
showing epoch instead of the correct time. I have assumed this is due to
the fact that we can fire up the web interface before the ntp has
completed setting the time. A refresh shows the correct date.
Some of the startup commands are backgrounded, so commands can sometimes
run before others have completed.
Code:
--------------------
/usr/sbin/ntpd -q -p pool.ntp.org
--------------------
This is the standard command to set the time (maybe with sudo).
Maybe a wait 5; before the openvpn command. If you like scripting, a
wait loop checking that the time is not epoch before proceeding.
I am just trying to eliminate one download and a extra command.
Again, thanks for doing this. :)
regards
Greg
------------------------------------------------------------------------
Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403
View this thread: http://forums.slimdevices.com/showthread.php?t=106895
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
