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.
__
This is the maintainer address of Debian's J
hod.java:597)
at
org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:177)
-Original Message-
From: Ludovic Claude [mailto:ludovic.cla...@laposte.net]
Sent: den 13 april 2011 23:28
To: Andreas Åkesson; 554...@bugs.debian.org
Subject: Re: Bug#554853: jetty: Jetty i
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, An
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:
false
2
104
107
jetty:con
On Fri, Nov 6, 2009 at 11:39 PM, Robert LeBlanc 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.
> http://blogs.webtide.com/ja
5 matches
Mail list logo
