[EMAIL PROTECTED] schrieb:
On 2005-06-25 15:29:19 -0400, <[EMAIL PROTECTED]> said:
I could not find any command to shutdown Lenya when running using
Jetty. There is no "stop" option in lenya.sh. Why not, and what is
the workaround?
I believe the workaround for stopping Lenya is to simply kill it. You
could have your init script write the lenya PID it a file in /var/run
and add an option to the init script for stopping it. Take look at some
of the other intit.d scripts for examples.
Yes, that is the standard for poorly designed programs. It feels like
a great way to cause memory leaks. I am hoping Jetty/Lenya is better
designed.
I'm not sure what you mean. A normal "kill" (without options) is the
normal way to signal a program to stop under Unix, what does this have
to do with Lenya's design and memory leaks ?
In any case since both Tomcat and Jetty are Java programs, it is "java"
you're sending the kill signal to.
So in lenya.sh you would start java in background and store its PID (and
not the lenya.sh's PID). The stop would kill that PID. I haven't tried
this in Lenya, but in another Cocoon application (cocoon.sh) and it
works fine.
AFAIK the only reason for the shutdown ports in programs like Tomcat or
Jetty is to provide a platform-independant way of shutting them down. 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. I assume the reason this isn't done is because
there is no standard location to put this PID file.
--
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
