[pkg-lighttpd] Bug#383425: lighttpd: foo

[Steve Langasek]

severity 383425 wishlist
thanks

On Thu, Aug 17, 2006 at 01:23:39AM -0700, Ken Bowley wrote:
> I wish to install lighttpd to use as a web server for a Ruby on Rails
> application, but it will not be running on port 80 (already used by
> Apache).  The postinst script fails on a new installation when Apache
> (or another daemon) is already bound to port 80.

> It is highly common to run lighttpd as a normal user on an unprivledged
> port port and have Apache act as a proxy in the Ruby on Rails community.

> Setting up lighttpd (1.4.11-7) ...
> Starting web server: lighttpd2006-08-17 01:08:10: (network.c.300) can't
> bind to port: localhost 80 Address already in use
>  failed!
> invoke-rc.d: initscript lighttpd, action "start" failed.
> dpkg: error processing lighttpd (--configure):
>  subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
>  lighttpd
> E: Sub-process /usr/bin/dpkg returned an error code (1)

And, how is this different from the behavior of any other webserver?  It's
perfectly normal for a server package to start its daemon at install time
and leave the package in an unconfigured state if this fails.  Surely you
can fix this by editing the config file for the package to change the port,
and then run dpkg --configure?

In any case, this is not a grave bug, it does not render the package
unusable or mostly so.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon at debian.org                                   http://www.debian.org/