> -----Original Message-----
> From: Rich Felker [mailto:dal...@aerifal.cx]
> Sent: Tuesday, March 18, 2014 1:12 PM
> To: Bryan Evenson
> Cc: Harald Becker; Laszlo Papp; busybox@busybox.net; Adam Tkáč
> Subject: Re: Ntpd config file support
> 
> On Tue, Mar 18, 2014 at 01:59:37PM +0000, Bryan Evenson wrote:
> > I'm also using ntpd with a Yocto Project based system, and I had
> > switched to using the full ntp package instead of the Busybox supplied
> > ntpd because of configuration. Within this build framework, I didn't
> > see an easy way to adjust the ntpd command line or to set its
> > configuration for the final built image. At the same time, I can
> > understand the resistance to adding another configuration file that
> > needs to be maintained.
> >
> > How about a set of ntpd menuconfig options to build the command line?
> > We could configure the default ntpd settings at build time, it
> > wouldn't add anything to the size of the final ntpd binary.
> 
> How is it hard? Just wrap ntpd with your own shell script called "ntpd" that
> parses your config file and passes the options on the command line to
> "busybox ntpd"... Or am I missing something?

Within my build framework this was not easy.  At least for me when I was just 
starting to use the Yocto Project for building my entire system image.  Within 
this framework it's not too hard to alter build configuration parameters or 
override userspace files for particular package.  I had assumed there was an 
init script provided by BusyBox (and I still had thought that up until Laszlo 
started this thread), so I first had an issue trying to find a non-existent 
file to override.

My next issue is that I look at this page: 
http://www.busybox.net/downloads/BusyBox.html when trying to figure out what 
command line options are available for a BusyBox command.  I'll do this before 
I change the BusyBox build to get an idea of what I need to do to control it.  
If you take a look at that page, ntpd is not listed.  So I didn't know how to 
start ntpd, and I didn't know what options were available for ntpd.  Given that 
start, I decided to use the full ntpd package instead of the Busybox-provided 
ntpd.

Harald had suggested an example startup script (I'm assuming under the 
examples/ directory of the Busybox source?).  With a working example and an 
easy place to find the ntpd command line options, I'd probably give the 
Busybox-provided ntpd a try.

Regards,
Bryan

> 
> Rich
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox

Reply via email to