Jetty vs. Tomcat: We do not care about startup time, since the production version of Lenya should rarely be restarted. Eyeballing it, Lenya on Jetty does seem faster than Lenya on Tomcat. I have not changed Apache to proxy to Lenya yet, but I doubt that adds much overhead. The difference is there is no init.d file for starting and stopping Lenya on Jetty.
I need: 1. A command to start Lenya that returns. lenya.sh starts Lenya, but never returns. That would stall the boot process if I call it in init.d. I need to research how Java can start and return. 2. A command to stop Lenya. To stop, I need to capture either Jetty's STOPKEY or the PID for the java process. Gregor had difficulty with the STOPKEY. Wolfgang had success with the PID. I'll try the PID first. 3. The Lenya console to be redirected to a log, preferably with rotation when it reaches a certain size or the month changes. I'll worry about that later. "there is no standard location to put this PID file." The OS standard locations do not matter. I will store it in the Lenya directory. > I do agree that it would be nice if the cocoon.sh (and hence the lenya.sh) > had "start" and "stop" options out-of-the-box, which wrote the PID > somewhere and used that. It sounds like I need to create a single shell file with start, stop, restart, and status commands. It will probably bypass lenya.sh and call java directly. If I get it working, it will be documented on my site (and Gregor can decide if it should be merged into trunk.) solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
