Control: tags -1 + wontfix
Control: close -1
This issue has been fixed in the jetty8 package, it uses authbind to
allow binding on privileged ports.
I'm closing this bug as wontfix since Jetty 6 is rather old and the
package is going to be removed.
--
To UNSUBSCRIBE, email to
Hi,
thank you for your answer. unfortunately it didn't change.
jetty-setuid.xml:
Configure id=Server class=org.mortbay.setuid.SetUIDServer
Set name=startServerAsPrivilegedtrue/Set
Set name=umask2/Set
Set name=uid104/Set
Set name=gid107/Set
!-- uncomment to change the limits on number of
Hello,
You should install the package libjetty-extra, it contains libsetuid.so
which will help you to give Jetty the priviledge to use a port under
1024. You will need to configure jetty-setuid.xml, in particular set the
startServerAsPrivileged property to true.
Ludovic
On 12/04/2011 10:54,
I'm having the same problems on jetty 6.1.24-6. Is there any system configs i
can/should alter to make this work?
/etc/default/jetty
NO_START=0
VERBOSE=yes
#JETTY_USER=jetty
JETTY_USER=root
JETTY_HOST=0.0.0.0
JETTY_PORT=80
jetty-setuid.xml:
Configure id=Server
On Fri, Nov 6, 2009 at 11:39 PM, Robert LeBlanc rob...@leblancnet.us wrote:
When setting JETTY_PORT=80, the server dies. There is a setuid option for
jetty that would allow it to run on port 80. Although an iptable's rule could
be created, Jetty should include this functionality.
5 matches
Mail list logo