Hi Harald, I am working on an init script which I will submit soon to the Yocto project if everything goes alright.
The idea is that I have an application on the embedded system where the user can configure the ntp peer. The application would then re-run and also enable the ntp daemon from busybox if it is not yet done so. I think the standard way to do it would be to use initscripts (sysv or systemd). It is not a problem to run busybox's ntpd with the right command line parameters on the fly, but automatically on boot, it is getting a bit more important if you know what I mean. It would be basically consistent with several other applets, namely: * syslogd * crond * httpd * udhcpcd * inetd ... etc. As for Zoltan, yes, I understood, and that is why I also mentioned he would be doing it in buildroot, which is somewhat similar to Yocto, but not quite. :) The point is that ntpd could be run from initscripts with a config file dedicated for it, but perhaps there are better solutions for this out there? Cheers, L. On Tue, Mar 18, 2014 at 12:43 PM, Harald Becker <ra...@gmx.de> wrote: > Hi Laszlo ! > >>it seems that the ntpd util currently does not support config >>files. > > The Busybox ntpd applet get all information it needs via command > line, so it doesn't need to read any config file. The config > files Zoltan mentioned are part of his distribution, not > Busybox. So what kind of config file feature do you need? > > -- > Harald _______________________________________________ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox