For the instructions on starting/stopping Lenya on Jetty using an
init.d script, see:
http://solprovider.com/lenya/jettyservice
Wait until tomorrow if you do not want Jetty/Lenya running as root.
And I'll be testing if Lenya starts after a reboot, so the website may
be flaky tonight.
== Notes
> This log only serves to show whether startup and shutdown worked OK.
That is correct. So where is the regular log?
Mostly followed Wolfgang's design.
Used a variable named "lenyadir" (defaults to $LENYA_HOME) many times.
Decided to use lenya.sh. Stored the PID in lenya.sh. Kill it in
init.d/lenya. Not the best design, but the least changes. (Better
solution suggested below.)
> You don't want a Servlet container to run as root. So if you
> start Lenya from an init.d script, do an su within it.
Oops. Forgot to su. Will fix very soon.
== "lenya.sh" ==
lenya.sh needs work. Why does it keep running? It should start java
and quit. Every java line should end in an ampersand (except CLI?)
The process ID for the top-level java process should be stored in
lenya.pid. (Wolfgang and I like that filename.)
It should check if lenya.pid exists before starting again. If the
file exists, try to stop the process before starting again. I think a
wait is needed; it complained the port was in use when I used the
restart option.
Add a stop command.
Are the options mutually exclusive: admin, profile, debug?
I have an unfinished version with the options:
lenya.sh [stop|start] [admin|profile|debug|cli] [CLI args]
Should I finish it? Is anyone interested?
solprovider
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
