From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Startup-script for ntpdc
Date: Mon, 15 Feb 2016 10:34:03 +0100 [thread overview]
Message-ID: <20160215093403.GD23517@pengutronix.de> (raw)
In-Reply-To: <4a922db4a3ba7d9008891e287426be37@mail.gmail.com>
Hi,
On Tue, Jan 26, 2016 at 11:17:51AM +0100, Simon Falsig wrote:
> I've noticed that ntpdc (in Networking Tools > ntp) comes with a
> startup-script
> enabled and installed in /etc/init.d by default. But is it just me, or
> does
> having a startup-script not really make sense for ntpdc, which essentially
> is
> just a client application to query and control ntpd?
>
> In any case, the installed startup-script doesn't work, the arguments
> don't seem
> to make sense, and judging from the name of the script and the given
> configurationfile (ntp-client in both cases), it seems to be aimed at
> ntpclient
> (which is a different program, available at Networking Tools > ntpclient)
> instead?
>
> Am I overlooking something obvious here, or does this just not make sense?
I think you're right. It doesn't make sense. I suppose there could be some
magic that requires ntpdc to be run once at startup, but from what I can
tell from the git history, this looks like an error during refactoring. I
don't think it does any harm so nobody noticed.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2016-02-15 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 10:17 Simon Falsig
2016-02-15 9:34 ` Michael Olbrich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160215093403.GD23517@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox