Modify

Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#2336 closed task (fixed)

Vendor zone for NTP

Reported by: freycinet Owned by: developers
Priority: high Milestone:
Component: packages Version:
Keywords: Cc:

Description

As per the requirements available from the NTP Pool project, obtain a NTP Pool Vendor Zone for OpenWRT, and modify the config files of the ntpclient, ntpd, openntpd packages and any other OpenWRT packages using pool.ntp.org to use this Vendor Zone.

Details available at http://www.pool.ntp.org/vendors.html

I was going to apply for the Vendor Zone for OpenWRT to save the developers time, but it is probably best that this is applied for and managed by a core developer.

Attachments (0)

Change History (5)

comment:1 Changed 10 years ago by florian

  • Resolution set to fixed
  • Status changed from new to closed

Actually nbd already applied for one and we will be starting chaning init scripts and configuration files accordingly.

comment:2 follow-up: Changed 10 years ago by nico

The pool is "[0-4].openwrt.pool.ntp.org", patches welcome ;)

comment:3 in reply to: ↑ 2 Changed 10 years ago by StHoffmann

Replying to nico:

The pool is "[0-4].openwrt.pool.ntp.org", patches welcome ;)

Today I tested this and could reach [0-3] but not 4.openwrt.pool.ntp.org despite trying this several times. Could anyone confirm that this is only temporarily, or was it meant to be [0-3].openwrt.pool.ntp.org?

Is this already in the sources? In my OpenWrt kamikaze 7.09 built 30-Sep-2007 it was not.

If this is clear, making a diff/patch from my configuration would be easy.

comment:4 Changed 10 years ago by agb

Default configs for chrony, ntpclient, ntpd, and openntpd fixed in [10189]

comment:5 Changed 10 years ago by StHoffmann

Patch submitted on openwrt-devel:
http://lists.openwrt.org/pipermail/openwrt-devel/2008-January/001524.html

Comments welcome.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.