Re: Configuring instances/app directly in SiteConfig.xml

On Jul 20, 2004, at 3:50 AM, Dev WO wrote:

>>> We've also got some problems when we use Monitor after modifying 
>>> directly the xml file (we stop Monitor before modifying):
>>> The instances and apps show up in Monitor, but if we change anything 
>>> regarding the previous app/instances, it erases everything we added 
>>> to the xml file. And if we try to change something to the 
>>> instances/apps we added directly, Monitor gives an error complaining 
>>> it doesn't exist (because it seems it erases it just after 
>>> submitting a modification).
>>
>> Monitor is just a frontend to wotaskd. In order to modify 
>> SiteConfig.xml manually you first have to stop wotaskd.
> Does that mean I have to stop all WO applications to update that file?!
> if yes, how Monitor is doing to modify this file without stopping the 
> applications?

Monitor talks to wotaskd. wotaskd talks to the applications. wotaskd 
records the configuration to disk. Why would wotaskd need to stop the 
applications?

The problem is that wotaskd doesn't try to check the file for changes; 
it doesn't expect that you will modify the file by hand - why would it? 
Why do you need to modify the file by hand at all (while using 
wotaskd/Monitor)?

Karl

--

Caffeine-free Diet Crystal Pepsi

Homepage:
      http://homepage.mac.com/khsu/index.html