On Sun, Jan 2, 2011 at 11:27 PM, Arno Töll wrote:
> The patch overrides the default dh_installinit call that dh(1) generates
> and replaces it with a non fatal variant by using --error-handler
> supported in recent versions of debhelper.
Thanks, comitted to SVN.
Olaf
--
To UNSUBSCRIBE, email
On 03-Jun-08, 15:24 (CDT), Pierre Habouzit <[EMAIL PROTECTED]> wrote:
> [lighttpd fails install if something else is already running on port 80]
>
> Well I reckon it's not really well documented, I'm not not sure where
> to put that. dpkg is maybe not the place to put that. I'll followup that
>
On Tue, Jun 03, 2008 at 07:42:55PM +, Stefan Monnier wrote:
> > Debian is intended to work "simply" for the most used scenario, and to
> > need a 10 liner configuration for the less common ones. It's more common
> > that people want their sole httpd to be started on install than users
> > ha
> Debian is intended to work "simply" for the most used scenario, and to
> need a 10 liner configuration for the less common ones. It's more common
> that people want their sole httpd to be started on install than users
> having lots of chroots.
Sure. As I said: "The default might be to activa
On Tue, Jun 03, 2008 at 01:52:12PM +, Stefan Monnier wrote:
> >> Of course, this problem is not specific to lighttpd. The same problem
> >> occurs with other daemons which you may notwant to enable system-wide
> >> but that users may want to use, such as MPD. Of course, the problem
> >> also
>> Of course, this problem is not specific to lighttpd. The same problem
>> occurs with other daemons which you may notwant to enable system-wide
>> but that users may want to use, such as MPD. Of course, the problem
>> also occurs in other circumstances, such as when creating a Debian
>> system
On Tue, Jun 03, 2008 at 06:03:52AM +, Stefan Monnier wrote:
> Package: lighttpd
> Followup-For: Bug #383425
>
> Of course, this problem is not specific to lighttpd. The same problem
> occurs with other daemons which you may notwant to enable system-wide
> but that users may want to use, such
Bastian Kleineidam wrote:
> Package: lighttpd
> Version: 1.4.18-1
> Followup-For: Bug #383425
>
> Hi,
>
> here is a little perl script that checks if a port is already used
> by trying to bind() to it. I propose in the postinst you do:
>
> if fresh_install:
> if port 80 is taken (by using th
On Wed, Nov 14, 2007 at 01:53:33PM +, M. Koehrer wrote:
> Hello!
> I also had a look to that issue.
> In my opinion, the difference is the postinst script in the .deb package.
> I compared it with the postinst script of an Apache2 package.
> In Apache2 there is the line
> invoke
Hello!
I also had a look to that issue.
In my opinion, the difference is the postinst script in the .deb package.
I compared it with the postinst script of an Apache2 package.
In Apache2 there is the line
invoke-rc.d apache2 start || true
to start the apache2 server.
In lighttpd the
On Sun, Jul 29, 2007 at 03:04:52PM +0200, Olaf van der Spek wrote:
> > you can't install a
> > server along another that listens on the same port without having
> > fixed one or another configuration file.
>
> Why not?
> You can't start it, sure.
and that sucks hard time. FWIW apache2 is starte
11 matches
Mail list logo
