Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: NTP Client as IoT2020 has no battery backup. #24

Closed
DanPlastina opened this issue May 7, 2017 · 9 comments
Closed

Suggestion: NTP Client as IoT2020 has no battery backup. #24

DanPlastina opened this issue May 7, 2017 · 9 comments

Comments

@DanPlastina
Copy link

It would be fantastic if an NTP client was added to facilitate setting the clock on power up.

@nospam2000
Copy link

nospam2000 commented May 8, 2017

Adding ntpd will be one of my first projects for a self-baked image.

Hopefully I can get it working as stratum 1 server with a locally connected GPS receiver and even with PPS, but this depends on the hardware and kernel drivers.

@jan-kiszka
Copy link
Collaborator

Busybox has a built-in service for this, we just lack its activation. But we are taking patches 😉.

@nospam2000
Copy link

nospam2000 commented May 8, 2017

BusyBox's ntp client is small, but also has limitations. A short look at its REAME says for example that is doesn't support multiple servers.
ntpd is not only an ntp client but also a ntp server.

Nevertheless BusyBox will be appropriate for many users.

@jan-kiszka
Copy link
Collaborator

Hmm, the code says the busybox client supports multiple servers. It also has an optional server mode as well, but I have no own experience to compare it to a full-blown one.

@nospam2000
Copy link

I have now ntpd running using the standard recipe from OpenEmbedded and an adapted config file. Do you want a patch or merge request or a description how to get it into the image?

@jan-kiszka
Copy link
Collaborator

Pull request, please. Regarding the style of the commit, follow other commits in this repo. The log should describe why we want this change and carry a signed-off according to https://developercertificate.org.

I would suggest to preconfigure things generically for ntpclient operation, using e.g. the parameters of http://www.pool.ntp.org/en/use.html.

Did you also try the busybox applet? In any case, please document the reason for choosing the full-featured one.

@nospam2000
Copy link

sorry, I won't submit a pull request, because I quit using yocto and switch to debian.

@jan-kiszka
Copy link
Collaborator

...at your own risk.
You will have to rebuild an undefined number of packages then (I think I cited a war story elsewhere). An own kernel will also be required unless you can even live without network (will improve with 4.12 and then significantly with 4.13).
If you want to do this properly, this can be an interesting tool to describe the process: https://github.com/ilbers/isar. We didn't follow this path for the IOT2000 due to the significant effort + the fact that users will still not be able to pull from arbitrary Debian repos.

@jan-kiszka jan-kiszka mentioned this issue Jun 1, 2017
@jan-kiszka
Copy link
Collaborator

Feature merged - thanks for the suggestion and inputs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants