From: devzero@web.de
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jeff Dike <jdike@addtoit.com>,
linux-kernel@vger.kernel.org,
User-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH 1/6] UML - Deal with host time going backwards
Date: Tue, 03 Jun 2008 21:59:13 +0200 [thread overview]
Message-ID: <303013682@web.de> (raw)
>> Protection against the host's time going backwards - keep track of the
>> time at the last tick and if it's greater than the current time, keep
>> time stopped until the host catches up.
>
>Strange. What would cause the host's time (or at least UML's perception
>of it) to go backwards?
mhh - what about admin`s/user`s stupidity ?
e.g.
0 * * * * root /usr/sbin/ntpdate some.time.server >/dev/null 2>&1
in root`s crontab.
if the hosts`s clock is running faster than clock on some.time.server, this would set host`s clock back in time every hour or so....
common malpractice regarding time-syncronization - have seen that more than once.
(and have to admit that i used that some years ago before i wasn`t aware that ntpd does handle that more intelligent)
_______________________________________________________________________
EINE FÜR ALLE: die kostenlose WEB.DE-Plattform für Freunde und Deine
Homepage mit eigenem Namen. Jetzt starten! http://unddu.de/?kid=kid@mf2
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
WARNING: multiple messages have this Message-ID (diff)
From: devzero@web.de
To: Andrew Morton <akpm@linux-foundation.org>
Cc: User-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] UML - Deal with host time going backwards
Date: Tue, 03 Jun 2008 21:59:13 +0200 [thread overview]
Message-ID: <303013682@web.de> (raw)
>> Protection against the host's time going backwards - keep track of the
>> time at the last tick and if it's greater than the current time, keep
>> time stopped until the host catches up.
>
>Strange. What would cause the host's time (or at least UML's perception
>of it) to go backwards?
mhh - what about admin`s/user`s stupidity ?
e.g.
0 * * * * root /usr/sbin/ntpdate some.time.server >/dev/null 2>&1
in root`s crontab.
if the hosts`s clock is running faster than clock on some.time.server, this would set host`s clock back in time every hour or so....
common malpractice regarding time-syncronization - have seen that more than once.
(and have to admit that i used that some years ago before i wasn`t aware that ntpd does handle that more intelligent)
_______________________________________________________________________
EINE FÜR ALLE: die kostenlose WEB.DE-Plattform für Freunde und Deine
Homepage mit eigenem Namen. Jetzt starten! http://unddu.de/?kid=kid@mf2
next reply other threads:[~2008-06-03 19:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 19:59 devzero [this message]
2008-06-03 19:59 ` [PATCH 1/6] UML - Deal with host time going backwards devzero
-- strict thread matches above, loose matches on Subject: below --
2008-06-03 19:02 [uml-devel] " Jeff Dike
2008-06-03 19:32 ` Andrew Morton
2008-06-03 19:43 ` Daniel Hazelton
2008-06-03 19:52 ` Nix
2008-06-03 20:07 ` Andrew Morton
2008-06-03 20:37 ` Daniel Hazelton
2008-06-03 21:00 ` Jeff Dike
2008-06-04 1:50 ` Eric W. Biederman
2008-06-04 3:15 ` Jeff Dike
2008-06-04 5:12 ` Daniel Hazelton
2008-06-04 14:31 ` Jeremy Fitzhardinge
2008-06-04 19:37 ` Jeff Dike
2008-06-04 20:05 ` Jeremy Fitzhardinge
2008-06-05 15:30 ` Jeff Dike
2008-06-05 18:14 ` Nix
2008-06-05 19:47 ` Jeff Dike
2008-06-05 21:41 ` Nix
2008-06-05 18:19 ` Nix
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=303013682@web.de \
--to=devzero@web.de \
--cc=User-mode-linux-devel@lists.sourceforge.net \
--cc=akpm@linux-foundation.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.