You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@jakarta.apache.org by James Taylor <jt...@nybor.com> on 2000/07/17 19:35:44 UTC
File locations and daemon behavior ( was Re: java.lang.NullPointerException )
> IMV Apache should NOT be using /home.
> According to the Linux File System Standard, /home is for users' home
> directories, and is commonly shared via NFS.
Exactly. Do most redhat install still use /home/httpd and /home/ftp ?
> It's so on my system, and when I upgrade Apache on one system, /home gets
> updated on all systems. Fortunately, I don't actually configure my web
> servers to ship any pages from /home/nobody.
>
> That's why I've aimed Tomcat at /var. It's consistent with some other
> software, including Postgresql, that RHS ships.
>
> I would be happy for tomcat's configuration files to be in
> /etc/httpd/conf/tomcat - it's consistent with jserv (and I for one would
> like them to look very similar).
Should they be so similar? Jserv is very apache specific, whereas tomcat is
entirely standalone. From my (admitedly debian biased) perspective, this
ought to look something like:
config in /etc/tomcat/
webapps in /var/tomcat
workdir in /var/cache/tomcat/
logs in /var/log/tomcat/
startup scripts in /usr/bin and probably a nice wrapper in /etc/init.d/
jars in /usr/share/java/repository or whatever your favorite repository is.
...which is how I would have it configured if I weren't isolating it to
/usr/local right now. Of course I'm using tomcat without apache (sometimes)
or with mod_jk.
I don't like the idea of putting logs in /etc/apache or /etc/httpd when
tomcat could be installed as a standalone application.
> btw Tomcat's a pretty funny daemon. It really needs to learn better
manners; having started,
> it should direct ALL its complains etc to one of its log files, not spew
heaps of stuff out on the terminal.
If you set this in yr server.xml:
<Logger name="tc_log"
path="logs/tomcat.log"
verbosityLevel = "INFORMATION"
/>
then logging will be directed to the specified file.
However I agree that it is annoying that tomcat does not behave like a
normal daemon. Ideally the startup script would not fork until tomcat
sucesfully starts, and then return some sort of status code. I've been
thinking about how to implement this, any thoughts?
James Taylor
NYBOR.com