From owner-freebsd-questions@FreeBSD.ORG  Sat Aug 12 11:25:26 2006
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: freebsd-questions@freebsd.org
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 835AF16A4DA
	for <freebsd-questions@freebsd.org>;
	Sat, 12 Aug 2006 11:25:26 +0000 (UTC)
	(envelope-from root@pukruppa.de)
Received: from moutng.kundenserver.de (moutng.kundenserver.de
	[212.227.126.177])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5677943D6E
	for <freebsd-questions@freebsd.org>;
	Sat, 12 Aug 2006 11:25:21 +0000 (GMT)
	(envelope-from root@pukruppa.de)
Received: from [213.146.114.24] (helo=reverse-213-146-114-24.cust.kamp-dsl.de)
	by mrelayeu.kundenserver.de (node=mrelayeu1) with ESMTP (Nemesis),
	id 0MKwpI-1GBrcG0FuI-0003JP; Sat, 12 Aug 2006 13:25:20 +0200
Date: Sat, 12 Aug 2006 13:42:49 +0200 (CEST)
From: "P.U.Kruppa" <root@pukruppa.de>
X-X-Sender: root@www.pukruppa.net
To: freebsd-questions@freebsd.org
Message-ID: <20060812133730.S1240@www.pukruppa.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Provags-ID: kundenserver.de abuse@kundenserver.de
	login:2446dbdf8275641f979193ced594c629
Subject: Bad system clock
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Aug 2006 11:25:26 -0000

Hi,

for some time now my system clock really goes wrong (some hours 
per day). Is there some simple way to find out if this is caused 
by a hardware or software problem?
By "simple" I mean without installing a different OS or buying a 
new computer?

Regards and thanks,

Uli.


*********************************************
* Peter Ulrich Kruppa - Wuppertal - Germany *
*********************************************