Daniel Hagerty wrote:
> "Sarton O'Brien" <bsd-xen@roguewrt.org> writes:
>
>   
>> This is more or less a curiosity ...
>>
>> I configured dom0 with ntpd and timed -F localhost assuming that the 
>> most accurate time keeping will be on the dom0. It seems though that 
>> dom0 cannot act as a master.
>>     
>
>     Why are you trying to run timed *and* ntpd?  timed is mostly a
> historic relic in this day and age.
>
>     No actual input on your problem...
>   

CURRENT's ntp has been less than perfect. I have another thread going 
atm where ntpd is panicing my kernel. Prior to that, ntp failed to 
service requests ... or did so intermittently .... on a domu, ntpdate on 
boot is useless.

Anyway, the point of my xen system is to play with stuff. I've never 
bothered with timed and unless I'm mistaken, it does not synchronise 
with an internet server therefore ntp seems to be appropriate for the 
time keeper. The example given in the NetBSD docs is of this scenario so 
I saw no problem, in-fact, from memory I think it was reccomended.

Is there documentation stating timed is deprecated? If it is merely 
historic, why is it in current? I found the use of broadcast and no 
config quite alluring due to the issues I've had with ntp ... and the 
frequency with which I create new domus.

Sarton