From: Stuart Howard <stuart.g.howard@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Losing time somewhere
Date: Wed, 31 Aug 2005 10:10:22 +0100 [thread overview]
Message-ID: <d5d1857a050831021070d9eb0e@mail.gmail.com> (raw)
In-Reply-To: <200508301838.43618.uwix@iway.na>
Thank you the the hwclock tip it will solve my problem exactly.
Unfortunatly it seems my problems were deeper and beyond the scope of this
thread really, the loss of time was due to "something" within the kernel
that I built last week I also realised that my hard disk performance
had fallen dramatically, again due to some option selected or not within
the .config.
After a 6 hour session of "tweaking" last night, I decided to take the
honourable way out and deleted the 2.6.12-r9 kernel and reverted to a 2.6.11.5
that came from a genkernel setup some time ago that has served me well for
the last few months.
Thanks for help on time issue, some reading to be done I think
stu
On 8/30/05, Uwe Thiem <uwix@iway.na> wrote:
> On 30 August 2005 15:17, Stuart Howard wrote:
> > thanks for the response
> >
> > So far as I can tell I have not had ntp on my system, I have not put
> > it on myself the only way it could have been on is if it were a
> > default during original install of Gentoo in which case --depclean
> > ought not to have removed it as it should "belong" to something [world
> > , system ]
> >
> > I may give up on chrony and put a ntp on and see if that cures it,
> > though I prefer not to just mask a problem if there is one, could a
> > clock slowdown be something as serious as an indication of hardware
> > problems?
>
> Not really since your clock is on time after a boot.
>
> Please understand that there are two "clocks" involved. One is a hardware
> clock. The other one is the "system clock" which is software. "date" shows
> the system clock. During the boot process, the content of the hardware clock
> is copied to the system clock. That's why your system clock is correct after
> booting. It also shows that your hardware clock is doing fine. Your system
> clock is misbehaving.
>
> Whatever the reason for its sluggishness, ntpd or ntpdate (using an ntp server
> near you) should solve. Or, since your hardware clock is alright, a simple
> "hwclock -ru" (if your clock is set to UTC) or "hwclock -r" (if not so)
> should do the trick. Let cron execute it every hour or so.
>
> Uwe
>
> --
> 95% of all programmers rate themselves among the top 5% of all software
> developers. - Linus Torvalds
>
> http://www.uwix.iway.na (last updated: 20.06.2004)
> --
> gentoo-user@gentoo.org mailing list
>
>
--
"There are 10 types of people in this world: those who understand
binary, those who don't"
--Unknown
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-31 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 8:52 [gentoo-user] Losing time somewhere Stuart Howard
2005-08-30 13:56 ` A. Khattri
2005-08-30 14:17 ` Stuart Howard
2005-08-30 14:20 ` John Jolet
2005-08-30 17:38 ` Uwe Thiem
2005-08-31 9:10 ` Stuart Howard [this message]
2005-08-31 9:43 ` Nick Rout
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d5d1857a050831021070d9eb0e@mail.gmail.com \
--to=stuart.g.howard@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox