Hello. For one timesync couldn't write to the rtc, so I commented out the lines in cpurc. Well, here timesync is not the problem, time is reported incorrectly, and I do not really know how to set it. I tried echoing unix time into '#r' and /dev/rtc, with no luck: $sysname# ls -l /dev/rtc --rw-rw-r-- r 0 bootes bootes 0 Apr 23 20:43 /dev/rtc $sysname# echo -n '1219699386' > /dev/rtc echo: write error: permission denied (on the hostowners console) Also cron still spews messages flooding it's log with lines like this: Aug 26 02:29:41 time went backward Which might be related to time issues..
rgds On Mon, 25 Aug 2008 20:54:53 +0200 [EMAIL PROTECTED] wrote: > > Well, i don't think I am starting two timesync, ps a shows only one: > > If Xen is anything to go by, time keeping is a problem in > virtualisation. And Erik is misguiding you :-) > > Thing is, if timesync is wresting with the clock as it seems to do if > two instances are running, it does consume a lot of cpu time, > according to experiences reported on this list. But it's possible > that timesync is wrestling with the virtual executive rather than with > another instance of itself. > > Would it hurt you to run without timesync? > > ++L > >
