From: Antonios C. <an...@it...> - 2003-12-04 14:15:24
|
Hi, newbie here. Sorry if I'm missing some obvious faq; no success googling. I deleted a file in the directory of a test context, and the log reads: *** The file /usr/local/Webware-0.8.1/WebKit/mytest/SecureCountVisits.py is no longer accessible. The server is restarting now. ThreadedAppServer: Shutting Down Stopping AutoReload Monitor Shutting down the AppServer Application is Shutting Down Application has been succesfully shutdown. AppServer has been shutdown Exiting AppServer The server claimed it would restart, whereas it actually shut down. Could this be a bug? Or have I not understood something? The same happens when I change Application.config: I get a message saying something like Application.config has changed, the server is restarting, but I have to start it after that. (Webware 0.8.1 on a Debian 3.0 running kernel 2.4.18 and Apache 1.3.26, using mod_webkit). By the way, great docs! Great docs! |
From: Ian B. <ia...@co...> - 2003-12-04 16:46:59
|
On Dec 4, 2003, at 8:14 AM, Antonios Christofides wrote: > Hi, newbie here. Sorry if I'm missing some obvious faq; no success > googling. > > I deleted a file in the directory of a test context, and the log reads: > > *** The file > /usr/local/Webware-0.8.1/WebKit/mytest/SecureCountVisits.py is no > longer accessible. The server is restarting now. > ThreadedAppServer: Shutting Down > Stopping AutoReload Monitor > Shutting down the AppServer > Application is Shutting Down > Application has been succesfully shutdown. > AppServer has been shutdown > > Exiting AppServer > > The server claimed it would restart, whereas it actually shut down. > Could this be a bug? Or have I not understood something? The same > happens when I change Application.config: I get a message saying > something like Application.config has changed, the server is > restarting, > but I have to start it after that. (Webware 0.8.1 on a Debian 3.0 > running kernel 2.4.18 and Apache 1.3.26, using mod_webkit). The auto-restarter exits the application with a magic error code (3). The AppServer shell script checks for this error code, and if it gets it then it restarts the server. I don't think the webkit init.d script checks for this code (nor does the NTService starter). > By the way, great docs! Great docs! Really? -- Ian Bicking | ia...@co... | http://blog.ianbicking.org |
From: Antonios C. <an...@it...> - 2003-12-08 10:45:55
|
> >By the way, great docs! Great docs! > > Really? I think that the documentation for such systems usually takes you through how to make an app, and in the end you can make an app but you don't understand how it works (as a result, when you start making a real app, you'll be at a loss and you won't know why it doesn't work). In contrast, the webkit's installation manual only tells you exactly what it's doing behind the scenes; meaning you know what's going on before you write your first line of code. And it's interesting that when you come to what you would expect to be the important part, that is, how to make an app, the manual essentially says "I don't know, look at the examples", and understandably so; because you can easily figure this out. |