On 2/13/2006 12:22 PM Mark Knecht wrote:
On 2/13/06, Drew Tomlinson <[EMAIL PROTECTED]> wrote:
Anyway, I really appreciate your thoughts. Because this box runs
MythTV, time is *VERY* important. Imagine my surprise when I went to
watch the first day of the Olympics on to find out that my re
Answer is at the bottom
On 2/13/06, Jeff <[EMAIL PROTECTED]> wrote:
> Hey Mark.
>
> I'd also like to pitch in here.
>
> Since about two weeks ago, my machines are no longer keeping time as
> well. I'm getting errors when my systems boot during sysinit - the clock
> script fails miserably, and some
Hey Mark.
I'd also like to pitch in here.
Since about two weeks ago, my machines are no longer keeping time as
well. I'm getting errors when my systems boot during sysinit - the clock
script fails miserably, and some systems it forces me into console to
try and correct the problem.
I'm not sure
On 2/13/06, Drew Tomlinson <[EMAIL PROTECTED]> wrote:
> Anyway, I really appreciate your thoughts. Because this box runs
> MythTV, time is *VERY* important. Imagine my surprise when I went to
> watch the first day of the Olympics on to find out that my recordings
> were off by over an hour and h
On 2/12/2006 8:01 PM Harry Putnam wrote:
Drew Tomlinson <[EMAIL PROTECTED]> writes:
The time server is a FreeBSD 6.0 box on my network. My other FreeBSD
box and two Windows boxes get time from it just fine. Even the Gentoo
box will set its clock with "ntpd -gq". I am currently using this
Drew Tomlinson <[EMAIL PROTECTED]> writes:
> The time server is a FreeBSD 6.0 box on my network. My other FreeBSD
> box and two Windows boxes get time from it just fine. Even the Gentoo
> box will set its clock with "ntpd -gq". I am currently using this
> brute force method via a cron job as a
6 matches
Mail list logo
