On Fri, Oct 17, 2008 at 7:09 AM, Chris [EMAIL PROTECTED] wrote:
2008/10/17 g [EMAIL PROTECTED]:
if you would like to make your life a little easier, set up one of
your local boxes, that has internet access, to act as a local server.
let it check 'outside' for time, then you can sync all boxes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tod Merley wrote:
snip
Time Server -- Often GPS NTP Time Server I suppose it adds a bit of
expense but the time accuracy would be increased.
syncing to a cell phone's clock would be very inexpensive. accuracy would
be of provider.
- --
tc,hago.
First of all, thanks for all the replies. Some useful suggestions in there
which I'll be trying this morning.
2008/10/17 Mikkel L. Ellertson [EMAIL PROTECTED]
runs /sbin/hwclock --utc --hctosys to sync the hardware clock to
the system clock.
But this is syncing the system clock to the
2008/10/17 Todd Denniston [EMAIL PROTECTED]
Mikkel L. Ellertson wrote, On 10/16/2008 05:23 PM:
What are you trying to do with this cron job? You are updating the
system clock from the hardware clock, and not the other way around,
as you say you are trying to do. The system does synchronize
2008/10/17 g [EMAIL PROTECTED]:
if you would like to make your life a little easier, set up one of
your local boxes, that has internet access, to act as a local server.
let it check 'outside' for time, then you can sync all boxes to a
local time server and *all* of you local network will be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris wrote:
Thanks for the idea but these machines are sent out to various sites,
snip
ok. if system time syncing is supper critical, have you considered time
sync with a radio clock? again, check '/usr/share/doc/ntp*'. and you
can google for
Chris wrote, On 10/17/2008 06:46 AM:
First of all, thanks for all the replies. Some useful suggestions in there
which I'll be trying this morning.
2008/10/17 Mikkel L. Ellertson [EMAIL PROTECTED]
runs /sbin/hwclock --utc --hctosys to sync the hardware clock to
the system clock.
But this is
Todd Denniston Todd.Denniston at ssa.crane.navy.mil writes:
1) you don't need to call hwclock while NTP is running to keep the hardware
clock synced to system time, the kernel hackers helpfully put a sneak
circuit in the ntp implementation in the _kernel_ such that if NTP declares a
good
Ian Burrell wrote, On 10/17/2008 02:40 PM:
Todd Denniston Todd.Denniston at ssa.crane.navy.mil writes:
1) you don't need to call hwclock while NTP is running to keep the hardware
clock synced to system time, the kernel hackers helpfully put a sneak
circuit in the ntp implementation in the
On Fri, Oct 17, 2008 at 05:42:49PM -0400, Todd Denniston wrote:
Ian Burrell wrote, On 10/17/2008 02:40 PM:
Todd Denniston Todd.Denniston at ssa.crane.navy.mil writes:
1) you don't need to call hwclock while NTP is running to keep the
hardware clock synced to system time, the kernel hackers
I've got an hourly cron job on some machines that runs /sbin/hwclock --utc
--hctosys to sync the hardware clock to the system clock. These machines
were recently upgraded from an old custom RH7.3 installation to a custom
spin of Fedora 9 and started to occassionally lock up - every day or three.
I
On Thu, Oct 16, 2008 at 8:19 AM, Chris Mocock
[EMAIL PROTECTED] wrote:
I've got an hourly cron job on some machines that runs /sbin/hwclock --utc
--hctosys to sync the hardware clock to the system clock. These machines
were recently upgraded from an old custom RH7.3 installation to a custom
Todd Denniston wrote:
If you don't have an ntp source, using /etc/adjtime (with `hwclock
--adjust` after appropriate disciplining), the quartz time of the
hardware clock can be SIGNIFICANTLY better than system time, so if you
pull the hardware clock into your system in a reasonable
13 matches
Mail list logo
