Right. This is very much the same way other services like Apache httpd
do things. The privileged process is there to catch signals and open
ports for listening. The unprivileged process does the actual work.
--David
Andrew Ralph Feller, afelle1 wrote:
> Thanks for the reply David!
>
> If you s
Thanks for the reply David!
If you startup jsvc and do "ps axu | grep jsvc", you will find two processes
with one being owned by root and the other by the non-root account. The
non-root process will actually handle the incoming requests, however the
root process is needed to bind to port 443 sinc
is good to calm them down.
Torsten
-Original Message-
From: David Smith [mailto:[EMAIL PROTECTED]
Sent: 30. oktober 2008 19:55
To: Tomcat Users List
Subject: Re: JSVC vs standard startup / shutdown scripts
>
> I don't have any personal issue with moving to running Tomcat directl
>
> I don't have any personal issue with moving to running Tomcat directly as
> the non-privileged account meant for Tomcat ...
Just to clarify, jsvc runs tomcat as an unprivileged user as well. One
advantage to jsvc is it allows tomcat to be run by itself without funky
iptables rules or a front-
Thanks for the response Torsten!
In our environment, the machines we have Tomcat running on strictly use
Tomcat 6, APR for SSL support, and we load balance applications through an
external load balancer. We have been able to get by without brining HTTPD
for things like mod_rewrite or any of the P
Hi Andrew,
We let all our Tomcats run on a non-privileged port and use some init script
using startup.sh/shutdown.sh, and have an Apache httpd forwarding requests with
AJP.
We then use Apache httpd for things like terminating SSL, do RADIUS or LDAP
authentication, load balancing several Tomcat
