> 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
