Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#18542 - [ifplugd] Wrong way to launch ntpdate

Attached to Project: Arch Linux
Opened by Thomas Jost (Schnouki) - Wednesday, 03 March 2010, 08:24 GMT
Last edited by Evangelos Foutras (foutrelis) - Wednesday, 26 September 2012, 04:06 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Thomas B├Ąchler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No


In the latest ifplugd release, ntpdate is run in the /etc/ifplugd/ifup.d/ It is done this way:

ntpdate | logger

In the previous version, NTP was handled by 2 lines:

/etc/rc.d/ntpdate restart
/etc/rc.d/ntpd restart

This made much more sense to me. For instance I don't use, but either or a server on my company's LAN. And I also like to have ntpd restarted when a local NTP server is found by dhcpcd.

Is there a reason to run ntpdate this way? If not, could the maintainer please change this to use rc-scripts again?

This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Wednesday, 26 September 2012, 04:06 GMT
Reason for closing:  Fixed
Comment by Evgenij Vdovin (evdovin) - Sunday, 11 July 2010, 13:39 GMT
I think that need to use two scripts: one for ntptade and one for ntpd, because not all people are uses ntp server, but client only.
Comment by Clemens Buchacher (drizzd) - Saturday, 28 April 2012, 19:33 GMT
I vote for simply removing entirely, or keep it as a disabled example. This goes far beyond the goal of the package (which is to determine whether or not the ethernet cable is plugged in), and the user is free to add scripts.
Comment by Clemens Buchacher (drizzd) - Saturday, 28 April 2012, 19:34 GMT