Project

General

Profile

Bug #1257

There is no per virtualhost error log

Added by Anonymous about 12 years ago. Updated almost 11 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
core
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Missing in 1.5.x:

Description

I have seen that lighttpd doesn't allow a per domain error-log. i have given this inside a virtual host block:
---------
$HTTPhost =~ "^(www.doc.com|doc.com|dom.com|www.dom.com)" {
server.errorlog = "/home/httpd/doc.com/stats/doc.com-error_log"
}
-----------

But lighttpd only honours the LAST errorlog directive, and all the error for all domains are sent to that log. Is this by design? Or is it a bug?

Thanks.

History

#1

Updated by darix about 12 years ago

  • Status changed from New to Fixed
  • Resolution set to worksforme

works as designed.

#2

Updated by Anonymous about 12 years ago

Could you please elaborate. Works as designed? Does it mean that lighty doesn't have a per virtualhost error log, or that it has and does work properly?

Thanks.

-- ligesh

#3

Updated by Anonymous about 12 years ago

Hi,

Without a per virtualhost error log, the entire vhost concept doesn't make any sense. As in, how do you expect a customer in a shared hosting setup to fix errors on his website? Viewing a particular domain's error log is a very critical feature.
Thanks.

-- ligesh

#4

Updated by darix about 12 years ago

yes lighttpd supports only one error log. but that doesnt render vhosts useless. vhosts work outside of shared hosting environments very well too. yes this is a missing features that makes it harder to use lighttpd in shared hosting environments.
but in the end it is your decision if lighttpd will work in your setup or not.

for 1.5 we plan to fix this.

#5

Updated by Anonymous over 11 years ago

  • Status changed from Fixed to Need Feedback
  • Resolution deleted (worksforme)

Is this in 1.5?

Robin

#6

Updated by stbuehler almost 11 years ago

  • Status changed from Need Feedback to Fixed
  • Resolution set to invalid

The only thing interesting in the error log for vhosts are the cgi and fastcgi application errors; which the applications could also log somewhere else.

No, it is not in 1.5, and i don't think it will come as the log interface has no connection context parameter.

Anyway, no bug here.

#7

Updated by stbuehler almost 11 years ago

  • Status changed from Fixed to Invalid

Also available in: Atom