So far no problems with taskset process to one cpu and ntpd still running. Let's see how long it lasts.<br>Rick<br><br><div class="gmail_quote">On Jan 21, 2008 7:34 PM, Alex Malinovich <<a href="mailto:demonbane@the-love-shack.net">
demonbane@the-love-shack.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Mon, 2008-01-21 at 12:06 -0600, Rick Page wrote:
<br>> When I scan my currently running processes, I do find an ntpd process<br>> running. I also see that the ut3-bin process is idling at around 9.5%.<br>> I'll have to check it later while people are connected. If anybody
<br>> would like to connect to it, it is at <a href="http://64.34.161.48:7877" target="_blank">64.34.161.48:7877</a>.<br>> Back to this ntpd process, I don't think I really need it and can I<br>> stop the daemon?
<br><br></div>It's been a few months since I've used Xen, but I'm pretty sure that by<br>default the domU's will keep their time synced with the dom0, so you<br>really don't need ntpd running in the guest. Just go ahead and kill it
<br>and see if it helps. Having your time always be accurate to a few<br>milliseconds is certainly nice but it is by no means a necessity for a<br>working system.<br><font color="#888888"><br>--<br>Alex Malinovich<br>Support Free Software, delete your Windows partition TODAY!
<br>Encrypted mail preferred. You can get my public key from any of the<br><a href="http://pgp.net" target="_blank">pgp.net</a> keyservers. Key ID: A6D24837<br><br></font></blockquote></div><br>