> I would really recommend against using rdate like this, it jumps the
> clock. ntpd skews the clock (makes it run slightly fast or slow until
> the time is correct), so you don't miss out on any seconds (which
> sometimes skips cron jobs, makes logging more confusing, and can
> cause a lot of trou
On Mon, 14 May 2007, Stuart Henderson wrote:
> On 2007/05/13 23:06, John Nietzsche wrote:
> > */5 * * * * /usr/sbin/rdate -4ncva
>
> -c corrects for leap seconds
>
> > */5 * * * * /usr/sbin/rdate -4cva gw |
>
> and here you do it again i.e
On 2007/05/13 23:06, John Nietzsche wrote:
> */5 * * * * /usr/sbin/rdate -4ncva
-c corrects for leap seconds
> */5 * * * * /usr/sbin/rdate -4cva gw |
and here you do it again i.e. you are correcting time coming from a
source which is alread
On 5/13/07, John Nietzsche <[EMAIL PROTECTED]> wrote:
In the other two boxes (lion and etosha) i have:
*/5 * * * * /usr/sbin/rdate -4cva gw |
Everything is working ok except because of those two boxes always have
a time about 20/22 seconds after my gateway time, like
> I decided to get the time syncronization for all those boxes. In the
> gateway machine, i managed to get the following in crontab:
>
> */5 * * * * /usr/sbin/rdate -4ncva
> ptbtime1.ptb.de | /usr/bin/logger -t NTP
> Everything is working ok except because of those tw
John Nietzsche wrote:
...
> Everything is working ok except because of those two boxes always have
> a time about 20/22 seconds after my gateway time, like in the output
> for date command:
>
> [EMAIL PROTECTED] date
> Sun May 13 23:04:35 BRT 2007
> [EMAIL PROTECTED] date
> Sun May 13 23:04:59 BRT
Dear gentleman/madam,
i have a home network composed of 1 gateway and two boxes. All of them
running openbsd 4.1 of course.
I decided to get the time syncronization for all those boxes. In the
gateway machine, i managed to get the following in crontab:
*/5 * * * * /u
7 matches
Mail list logo
