Ntpd config file support
Laszlo Papp
lpapp at kde.org
Wed Mar 19 03:35:40 UTC 2014
On Tue, Mar 18, 2014 at 10:30 PM, Xabier Oneca -- xOneca
<xoneca at gmail.com> wrote:
> Hello,
>
> 2014-03-18 22:17 GMT+01:00 Ralf Friedl <Ralf.Friedl at online.de>:
>>> > Usually scripts in/etc/init.d use /etc/default/* as config values
>>>
>>> > (some distros, even using them as main config files). The scripts that
>>> > Laszlo posted fit that pattern.
>>> Not quite; actually "/etc/default" is more like a Debian, et al,
>>> pattern. OpenWrt will use something. Yocto uses something else, etc.
>>> And for what it is worth, buildroot is also strange with
>>> "/etc/default/ntpd" without any busybox indication.
>>
>> Which again shows that distributions are different, so which distibution
>> style should Busybox pick? It is up to the distribution to provide the right
>> information to the program.
>
> Just to note, OpenSUSE also uses /etc/default, and not only for
> daemons (e.g. in my computer are grub, nss, splashy, su and useradd
> config files in there). I'm not saying it is the best place for config
> files, but I usually use it (not in buildroot) to store similar config
> files loaded from init scripts.
I think you missed the "et al" part. I explicitly said "Debian, et
al", but let us not play name games. The main message is that we saw
four different ways right in the beginning of the thread, and guess
what: the "complete ntpd" implementation unified it. They were able to
make it!
More information about the busybox
mailing list