I think the way to go for this is:
-fake a sensor inside ntpd
-that sensor must be specifically asked for, say, with sensor
local-clock or the like
-make sure ntpd only ever uses that in absence of anything else
--
Henning Brauer, h...@bsws.de, henn...@openbsd.org
BS Web Services,
On 2012/09/07 20:16, Mike. wrote:
On 9/7/2012 at 6:35 PM Patrick Wildt wrote:
|I have machines which might not have an internet connection, but still
|need to
|be synchronized,
|even if the time's not correct. What's important is, that every
machine in
|the
|network has the
|same time.
Could I ask what your use-case is?
-E
On Fri, Aug 24, 2012 at 01:41:21PM +0200, Patrick Wildt wrote:
the diff below adds an option to the ntpd(8), which has him provide
time, even though he's not synced.
ok?
Index: ntpd.8
I have machines which might not have an internet connection, but still need to
be synchronized,
even if the time's not correct. What's important is, that every machine in the
network has the
same time. Also the ntp server doesn't have a sensor to synchronize to.
Patrick
Am 07.09.2012 um 17:33
On 9/7/2012 at 6:35 PM Patrick Wildt wrote:
|I have machines which might not have an internet connection, but still
|need to
|be synchronized,
|even if the time's not correct. What's important is, that every
machine in
|the
|network has the
|same time. Also the ntp server doesn't have a sensor to
the diff below adds an option to the ntpd(8), which has him provide
time, even though he's not synced.
ok?
Index: ntpd.8
===
RCS file: /cvs/src/usr.sbin/ntpd/ntpd.8,v
retrieving revision 1.31
diff -u -r1.31 ntpd.8
--- ntpd.8
