* Sylvain Wallez: > Mark Lundquist wrote: > > > ear devs, > > > > like to use cocoon.sh "as is", configuring it from without by means > > f a wrapper script. Using cocoon.sh without modification makes it > > asier to take Cocoon version upgrades. > > > > here is one thing, though, that I still have to change. I use the > > JB "daemontools" package to run all my Jetty+Cocoon instances under > > upervision and provide for automatic startup at boot-time. This nly > > works if I change cocoon.sh to exec the Java interpreter without > > orking. > > > What do you mean by "without forking" ? The shell has to lauch the JVM > in a separate process. Or do I miss something?
The shell builtin ��exec�� replaces the current shell process by the specified command. If you don't do that, both sh and java run until Jetty is stopped. FYI the FreeBSD port of Cocoon has already integrated this patch: @@ -111,7 +110,7 @@ # ----- Set Local Variables ( used to minimize cut/paste) # --------------------- -JAVA="$JAVA_HOME/bin/java" +JAVA="exec $JAVA_HOME/bin/java" Best regards, -- Jean-Baptiste Quenot Anyware Technologies http://www.anyware-tech.com/
