Hi all Apologies if this has been covered on the list, but I have been unable to find anything in the archives ...
One of Chuck's recent postings that recommended using ThreadedAppServer over AsyncThreadedAppServer got me to thinking about Monitor.py and what it uses. On checking, I realised that its hard-coded to use AsyncThreadedAppServer. Quick as a flash, I changed this to use ThreadedAppServer and recieved the following stream of output when running "./Monitor.py start daemon": <usual startup verbose stuff> ... Waiting for start No Response from AppServer Waiting for start No Response from AppServer Waiting for start No Response from AppServer Waiting for start No Response from AppServer Waiting for start No Response from AppServer Waiting for start No Response from AppServer Waiting for start No Response from AppServer Waiting for start No Response from AppServer Waiting for start Couldn't start AppServer Killing AppServer ... It seems to behave like this regardless of if I run as 'daemon' or not. Given that ThreadedAppServer is more stable, I'd rather be using this if at all possible - is there perhaps a fix for this in CVS (or a few quick changes I can make ... ?). I am using 0.5.1rc3. Thanks, Mark _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
