Re: [gentoo-java] tomcat permissions

["William L. Thomson Jr." <wlt@obsidian-studios.com>]

On Mon, 2006-08-07 at 14:09 -0400, Jesse V Griffis wrote:
>
> I have tomcat running as tomcat:tomcat.  I have my normal user added to the 
> 'tomcat' group, so that after tomcat auto-deploys the new webapp and then 
> I've gone and done some more work, I can run ant again and the delete of the 
> existing webapp works quietly - without being group writable I can't do that 
> automatically.

Ok that makes sense and I was assuming you were doing something along
those lines. I don't will see if I can find a reason why group writable
permissions are not set. If I can't then I will address ebuilds so the
webapps dir is group writable.
> 
> As for my "little more investigation", it's apparently not in 
> start-stop-daemon at all.  I found an older machine with a different init 
> script that just calls catalina.sh:

Yeah that's the nastiness. Avoid that, all new Tomcat ebuilds 5.0.28 and
5.5.17 use a gentoo specific init script. We don't hack or call
catalina.sh anymore.

> start-stop-daemon --start --quiet --chuid tomcat:tomcat --exec 
> ${CATALINA_HOME}/bin/catalina.sh -- start
> 
> That works as expected.  The ps output appears nearly identical whether I use 
> this or the current 5.5 script, the only difference being that the current 
> one includes more under "-classpath".

Well catalina.sh is part of several scripts for Tomcat. One of the ones
it calls is setclasspath.sh. Our init script basically consists of the
*nix specific parts of catalina.sh and setclasspath.sh compacted :)

Our init script should start and stop tomcat more reliably. With a
occasional hiccup on restart. Eventually I will replace it with the init
script a Tomcat dev made, but I have to hack/patch that to make it
Gentoo specific. So it is down the road a bit. Unless there is a dire
need.

-- 
Sincerely,
William L. Thomson Jr.
Obsidian-Studios, Inc.
http://www.obsidian-studios.com

-- 
gentoo-java@gentoo.org mailing list