In response to John Webster :
--On Friday, December 21, 2007 13:51:29 -0500 Bill Moran wrote:
In response to John Webster :
Not generally suitable for cron because it can take longer to slew
than it does for the next cron execution to occur, which would then
result in multiple
On Tue, Dec 18, 2007 at 11:02:12AM -0500, Bill Moran wrote:
In response to Michael W. Lucas :
Hi,
Been searching around without results:
Has anyone come up with a decent way to do timekeeping on a jail
server? ntpd(8) binds to all addresses, and I'd rather not do a
ntpdate out
In response to shinny knight [EMAIL PROTECTED]:
On Tue, Dec 18, 2007 at 11:02:12AM -0500, Bill Moran wrote:
In response to Michael W. Lucas :
Been searching around without results:
Has anyone come up with a decent way to do timekeeping on a jail
server? ntpd(8) binds to all
--On December 21, 2007 11:23:03 AM -0500 Bill Moran [EMAIL PROTECTED] wrote:
In response to shinny knight [EMAIL PROTECTED]:
The reason that is not recommended is that it results in sudden steps
of the clock. Occasionally, these steps go backwards. Software that
is very sensitive to
In response to John Webster [EMAIL PROTECTED]:
--On December 21, 2007 11:23:03 AM -0500 Bill Moran [EMAIL PROTECTED] wrote:
In response to shinny knight [EMAIL PROTECTED]:
The reason that is not recommended is that it results in sudden steps
of the clock. Occasionally, these steps
--On Friday, December 21, 2007 13:24:40 -0500 Bill Moran [EMAIL PROTECTED]
wrote:
In response to John Webster [EMAIL PROTECTED]:
--On December 21, 2007 11:23:03 AM -0500 Bill Moran [EMAIL PROTECTED]
wrote:
In response to shinny knight [EMAIL PROTECTED]:
The reason that is not
On Dec 21, 2007, at 10:24 AM, Bill Moran wrote:
ntpdate -B should slew the time slowly. (According to the manpage.)
Not generally suitable for cron because it can take longer to slew
than it does for the next cron execution to occur, which would then
result in multiple ntpdate programs
In response to John Webster [EMAIL PROTECTED]:
--On Friday, December 21, 2007 13:24:40 -0500 Bill Moran [EMAIL PROTECTED]
wrote:
In response to John Webster [EMAIL PROTECTED]:
--On December 21, 2007 11:23:03 AM -0500 Bill Moran [EMAIL PROTECTED]
wrote:
In response to shinny
--On Friday, December 21, 2007 13:51:29 -0500 Bill Moran [EMAIL PROTECTED]
wrote:
In response to John Webster [EMAIL PROTECTED]:
Not generally suitable for cron because it can take longer to slew
than it does for the next cron execution to occur, which would then
result in multiple
In response to John Webster [EMAIL PROTECTED]:
--On Friday, December 21, 2007 13:51:29 -0500 Bill Moran [EMAIL PROTECTED]
wrote:
In response to John Webster [EMAIL PROTECTED]:
Not generally suitable for cron because it can take longer to slew
than it does for the next cron
Hi,
Been searching around without results:
Has anyone come up with a decent way to do timekeeping on a jail
server? ntpd(8) binds to all addresses, and I'd rather not do a
ntpdate out of cron.
Thanks,
==ml
--
Michael W. Lucas[EMAIL PROTECTED], [EMAIL PROTECTED]
In response to Michael W. Lucas [EMAIL PROTECTED]:
Hi,
Been searching around without results:
Has anyone come up with a decent way to do timekeeping on a jail
server? ntpd(8) binds to all addresses, and I'd rather not do a
ntpdate out of cron.
I'm not entirely sure I comprehend where
On Tue, Dec 18, 2007 at 11:02:12AM -0500, Bill Moran wrote:
In response to Michael W. Lucas [EMAIL PROTECTED]:
Hi,
Been searching around without results:
Has anyone come up with a decent way to do timekeeping on a jail
server? ntpd(8) binds to all addresses, and I'd rather not do
13 matches
Mail list logo
