Hello All!
We run a small server on Debian Testing (this is bad, we know ^^) and
today, we possibly encountered a bug.
The server has 3 users "host", so 3 homes and www/ in each one:
/home/host1/www, /home/host2/www and /home/host3/www
lighttpd.conf includes several vhosts as follow:
$HTTP["host"] =~ "^host1.net$" {
server.document-root = "/home/host1/www"
server.errorlog = "/home/host1/error.log"
accesslog.filename = "/home/host1/access.log"
server.error-handler-404 = "/e404.php"
}
$HTTP["host"] =~ "^host2.net$" {
server.document-root = "/home/host2/www"
server.errorlog = "/home/host2/error.log"
accesslog.filename = "/home/host2/access.log"
server.error-handler-404 = "/e404.php"
}
$HTTP["host"] =~ "^host3.net$" {
server.document-root = "/home/host3/www"
server.errorlog = "/home/host3/error.log"
accesslog.filename = "/home/host3/access.log"
server.error-handler-404 = "/e404.php"
}
www-data is in host1, host2 and host3 groups
If say /home/host2 has wrong permissions (700 recursively for instance,
lighttpd can't access to access.log and error.log), and /home/host3 have
right permissions (770 in this case),
/etc/init.d/lighttpd start
lighttpd claims to start but doesn't actually.
When removing the $HTTP["host"] =~ "^host3.net$" , lighttpd reports the
error stating that it can't access to access.log and error.log and fails
to start.
Can someone please confirm that possible bug in this version of
lighttpd?
$ apt-cache policy lighttpd
lighttpd: Installed : 1.4.19-2
Thanks for reading!
on 11.05.2008 12:25

