BrianB2
July 26th, 2006, 12:36 PM
Sorry if this is an old question, but I've really tried hard to find the solution. It is difficult for me to think of search terms that cover my question without also hitting loads of irrelevant stuff.
I've used tomcat for years, but only with a manual install and running it as root. I've just installed the package on my new 6.06 system with synaptic. This version runs chrooted as a system user called tomcat5.
When I configure server.xml to listen on port 8080, it works fine. However, I want/need it to run as a standalone web server (i.e. without an apache front-end) by listening on port 80. In this case, it fails with java.netBindException: Permission denied:80.
I realise that processes running as root are allowed to open any socket number smaller than 1024. I also realise that some programs have special configurations for opening/using their specific sockets while chrooted (e.g. mysql, hamachi).
Is there a general technique for assigning permission to a non-root user for access to a specific port or set of ports below the 1024 "water line", or am I dealing with a specific tomcat deficiency or configuration issue?
I've used tomcat for years, but only with a manual install and running it as root. I've just installed the package on my new 6.06 system with synaptic. This version runs chrooted as a system user called tomcat5.
When I configure server.xml to listen on port 8080, it works fine. However, I want/need it to run as a standalone web server (i.e. without an apache front-end) by listening on port 80. In this case, it fails with java.netBindException: Permission denied:80.
I realise that processes running as root are allowed to open any socket number smaller than 1024. I also realise that some programs have special configurations for opening/using their specific sockets while chrooted (e.g. mysql, hamachi).
Is there a general technique for assigning permission to a non-root user for access to a specific port or set of ports below the 1024 "water line", or am I dealing with a specific tomcat deficiency or configuration issue?