> Knowing there are actually two clocks running in my server,
> the Linux System time and the Hardware Clock. We're trying
> now to sync the System time with the hardware clock every
> hour using a cron job.
Why? sync which way? do you know which is more accurate?
I didn't think anything use
there's no script written
on syncing the time in any cron job previously)
Desmond Foo
- Original Message -
From: "Hiten Desai" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 17, 2002 4:50 PM
Subject: Re: System Time Problem
> are your so
thanks hiten
i checked time of hardware and software its remain same.
and the up time of my server one day before
so what would be the exactily the problem
i have 180 users on the this server.
ravi
On Thu, 17 Oct 2002, Hiten Desai wrote:
> are your software and hardware clocks showing
> the
are your software and hardware clocks showing
the same time ?
and wht is the uptime ?
Hiten.
--- Desmond Foo <[EMAIL PROTECTED]> wrote:
> Dear All,
>
> I've got an IBM x230 Server here running on Redhat Linux 6.2. The
> server executes a set of scheduled batch jobs everyday based on a
> specif
I've got an IBM x230 Server here running on
Redhat Linux 6.2. The server executes a set of scheduled batch jobs everyday
based on a specific time set in crontab. Each time before the cron jobs are
executed, the starting and the ending of the cron job execution times are
captured a
Dear All,
I've got an IBM x230 Server here running on Redhat
Linux 6.2. The server executes a set of scheduled batch jobs everyday based on a
specific time set in crontab. Each time before the cron jobs are executed, the
starting and the ending of the cron job execution times are captured a
su -c 'date -s "8:00am"'
-- Generated Signature --
Most general statements are false,
including this one.
-- Alexander Dumas
-- End Sig --
___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/re
On Tue, 02 Jan 2001, Anthony E . Greene wrote:
> On Tue, 02 Jan 2001 20:05:36 John Aldrich wrote:
> >A good util is "rdate" to sync your pc clock with an atomic
> >clock over the 'Net.
>
> The only problem with rdate for non-realtime apps is that you have to jump
> through hoops to see if it fai
On Tue, Jan 02, 2001 at 09:40:48PM -0500, Anthony E . Greene wrote:
> >
> >Just throwing some obvious errors at it, it does return 1 in limiting
> >testing. FWIW.
>
> That blurb is in the version that shipped with RH6.2 and I have not found an
> error condition that results in a nonzero exit code
On Tue, 02 Jan 2001 21:28:01 Hal Burgiss wrote:
>On Tue, Jan 02, 2001 at 09:18:37PM -0500, Anthony E . Greene wrote:
>> The only problem with rdate for non-realtime apps is that you have
>> to jump through hoops to see if it failed. It _always_ gives an exit
>> code of zero, no matter what errors
On Tue, Jan 02, 2001 at 09:18:37PM -0500, Anthony E . Greene wrote:
> On Tue, 02 Jan 2001 20:05:36 John Aldrich wrote:
> >A good util is "rdate" to sync your pc clock with an atomic
> >clock over the 'Net.
>
> The only problem with rdate for non-realtime apps is that you have
> to jump through h
On Tue, 02 Jan 2001 20:05:36 John Aldrich wrote:
>A good util is "rdate" to sync your pc clock with an atomic
>clock over the 'Net.
The only problem with rdate for non-realtime apps is that you have to jump
through hoops to see if it failed. It _always_ gives an exit code of zero,
no matter what
On Tue, 02 Jan 2001, John N. Alegre wrote:
> I am running RedHat 6.1/6.2 on two towers and a Think Pad. Both the towers
> switched the year just fine, but the laptop booted Monday morning with a date
> in 1999 and a time seven hours off. I used the control-panel time machine and
> changed the da
Your laptop's system clock is behind. Once you set the time again, open
up a command prompt, and, as root, run "hwclock systohc" to set the
hardware clock.
On Tue, 2 Jan 2001, John N. Alegre wrote:
> I am running RedHat 6.1/6.2 on two towers and a Think Pad. Both the towers
> switched the year
I am running RedHat 6.1/6.2 on two towers and a Think Pad. Both the towers
switched the year just fine, but the laptop booted Monday morning with a date
in 1999 and a time seven hours off. I used the control-panel time machine and
changed the date and time and selected "Set System Time".
Afte
At 12:31 2000-05-23 +0430, Redhat Mailing List wrote:
>After some days since soft and hard clock were sync'ed using
>'date' and 'setclock', it is seen a two minutes differnce
>between them (soft one is late).
> Is there any bug with time keeping part of linux or i should
>sync them manually ,using
Hi
Here is a problem with the time system of Linux Mandrake 6.1.
After some days since soft and hard clock were sync'ed using
'date' and 'setclock', it is seen a two minutes differnce
between them (soft one is late).
Is there any bug with time keeping part of linux or i should
sync them manua
17 matches
Mail list logo
