| 1 |
James <wireless@×××××××××××.com> [14-09-30 14:24]: |
| 2 |
> <meino.cramer <at> gmx.de> writes: |
| 3 |
> |
| 4 |
> |
| 5 |
> > Unfortunately, ntp-client is configured via rc-update (added to |
| 6 |
> > "default") but after plugging in LAN the interface eth0 comes |
| 7 |
> > up and I have access via ssh...but the date is set to the beginnig |
| 8 |
> > of the UNIX epoch. I have to call ntp-client by hand. |
| 9 |
> |
| 10 |
> Meino, |
| 11 |
> |
| 12 |
> |
| 13 |
> Make sure your system time (hwclock) is properly set upon bootup. |
| 14 |
> Since you are running on an embedded hardware board, I'd look at |
| 15 |
> those docs and find a forum as to the specifics of how the hardware |
| 16 |
> clock is set and maintained on the board. Once you get it close, |
| 17 |
> then ntp should be configuration. |
| 18 |
> |
| 19 |
> man hwclock |
| 20 |
> |
| 21 |
> hth, |
| 22 |
> James |
| 23 |
> |
| 24 |
> |
| 25 |
> |
| 26 |
> |
| 27 |
> |
| 28 |
|
| 29 |
Hi James, |
| 30 |
|
| 31 |
...the system has no built-in RTC which still runs if the system is |
| 32 |
powered off. |
| 33 |
After power is up and eth0 is alive, the time/date has to be set via |
| 34 |
ntp-client. The rest already working. |
| 35 |
I called |
| 36 |
/etc/init.d/ntp-client start |
| 37 |
after booting the little beast and plugging in the RJ45 and everything |
| 38 |
else was fine. |
| 39 |
Currently I am experimenting with chrony (emerging). |
| 40 |
Will see, if this will make a difference ;) |
| 41 |
|
| 42 |
Best |
| 43 |
mcc |
Archives