Would you mind looking into lighttpd-angel (/usr/sbin/lighttpd-angel),
which was added to lighttpd upstream (and the debian package) almost 7
years ago as a possible fix to your upstream bug report?
Best wishes,
Mike
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
Hi team member,
Angel is a 2.0 thing (mostly) AFAIK.
On Sat, Apr 5, 2014 at 8:33 PM, Michael Gilbert mgilb...@debian.org wrote:
Would you mind looking into lighttpd-angel (/usr/sbin/lighttpd-angel),
which was added to lighttpd upstream (and the debian package) almost 7
years ago as a possible
Hi,
as lighttpd needs to be able to reopen the logfiles after logrotate, the www-
data user needs +rw.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
2010/3/7 Stefan Bühler light...@stbuehler.de:
Hi,
as lighttpd needs to be able to reopen the logfiles after logrotate, the www-
data user needs +rw.
See http://redmine.lighttpd.net/issues/show/1271
Use a pipe logger.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
Package: lighttpd
Version: 1.4.13-8
Severity: normal
Hi,
/var/log/ligghtpd/*.log is readable and writeable by www-data. User www-data
should not have this access.
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture:
5 matches
Mail list logo