cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <>
Subject Re: request
Date Wed, 01 Sep 2004 23:14:30 GMT
Steven Noels wrote:
> On 01 Sep 2004, at 23:19, Sylvain Wallez wrote:
>> Mark Lundquist wrote:
>>> Dear devs,
>>> I like to use "as is", configuring it from without by means 
>>> of a wrapper script.  Using without modification makes it 
>>> easier to take Cocoon version upgrades.
>>> There is one thing, though, that I still have to change.  I use the 
>>> DJB "daemontools" package to run all my Jetty+Cocoon instances under 
>>> supervision and provide for automatic startup at boot-time.   This 
>>> only works if I change to exec the Java interpreter without 
>>> forking.
>> What do you mean by "without forking" ? The shell has to lauch the JVM 
>> in a separate process. Or do I miss something?
> I'm using - which has a native part 
> doing the daemonizing of the VM. I had a look at commons-daemon and 
> DJB's daemontools as well, but finally sticked with wrapper - it worked 
> as promised and didn't require any exotic thinking so common to DJB's 
> tools. All three of them require you somehow to "unfold" what is 
> transcribed/constructed in the shell script into a one-line 
> JVM invocation. Doing an "echo" at the end will help you to find out 
> classpath, class to be invoked, etc etc...
> Since this is all system-dependent, I wonder if we could offer init-v 
> like shell scripts with Cocoon. Most of those which came with other Java 
> apps didn't work as expected on my system (like forking into another user).

here is the jetty script I use for my server (uses the Loader and 
deamontools' setuidgid) [taken from the jetty one and modified a little bit]


View raw message