1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

two time sync questions

Discussion in 'Tomato Firmware' started by Odin-60, Mar 9, 2007.

  1. Odin-60

    Odin-60 LI Guru Member

    Tomato Version 1.04.0944 on WRT54GL

    1) I'm surprised that the internal clock of the WRT54 needs
    to be adjusted by approx. +1 sec per hour. Is this normal?

    2) Is it possible to stop ntpsync leaving messages in the
    syslog? I'm running ntpsync every hour (for the reason
    mentioned above), so the log file is quickly filled up with
    unneeded messages.

    thank you in advance for enlightening me
  2. Odin-60

    Odin-60 LI Guru Member

    Oops, I just notice that it's in fact cron that is responsible for
    logging all its jobs. So let me rephrase my question #2:

    How can I stop cron from logging the hourly starting of ntpsync?
  3. der_Kief

    der_Kief Super Moderator Staff Member Member

    this seems to be normal. On my WRT54GL time is syncronized every 6 hours and there is always a time difference between 6-8sec.
    For your second question you have to wait till an expert :wink: has a solution. An alternative is a email request to Jon.

  4. Odin-60

    Odin-60 LI Guru Member

    Jon must have read my posting;
    logging of cron events can be turned off in v 1.05.
    Thank you!

  5. bokh

    bokh LI Guru Member

    Regarding the +1 sec/hour: I think the Broadcom processor's systemclock inside a Linksys isn't as accurate as -let's say- the average Sun Sparc64 or other high-end CPU. You get what you pay for, but as long as you sync it every couple of hours you're set...
  6. Odin-60

    Odin-60 LI Guru Member

    Strange that I never noticed this "problem" when I was still
    using DD-WRT. Its ntp client does not log the adjustment!
  7. MelechRic

    MelechRic LI Guru Member

    If you execute the sync manually from the command line you'll see the adjustment. I can confirm that it's around 1-2 seconds / hour regardless of the firmware you're using.

Share This Page