Project

General

Profile

Actions
Copy link

Feature #822

closed

Pipe support to error log(server.errorlog), support of multiple workers

Added by Anonymous over 18 years ago. Updated over 16 years ago.

Status:
Fixed
Priority:
Normal
Category:
core
Target version:
-
ASK QUESTIONS IN Forums:

Description

Hi, i have multiple workers, and only one worker can write error log.

I don't have this problem with writing of access logs because mod_accesslog support this:

"if the name starts with a '|' the rest of the name is taken as the name of a process which will be spawn and will get the output

accesslog.filename = "|/usr/sbin/cronolog /web/logs/%Y/%m/%d/access.log" 
"

How about to add same feature to "server.errorlog".

Error logs are very important to me and I can't ignore them.

-- adrenalinup

Actions
Copy link
 #1

Updated by Anonymous over 17 years ago

an implementation for using pipes for error log is available from TRAC 296 :

http://trac.lighttpd.net/trac/ticket/296

and is already included with some distributions of lighttpd like the one provided by gentoo

Actions
Copy link
 #2

Updated by Anonymous about 17 years ago

please note that pipe logging appears to bog down lighty seriously under high load.
i tried cronolog for accesslog on a server receiving ~60 hits/sec (lighty 1.4.15 back then i think)
and it would quickly slow down to a crawl.

out of curiousity i later tried and fed the normal on-disk accesslog to cronolog in realtime
with "tail -f" - worked for days without problems.

i guess buffering is needed to make pipe logging feasible for high traffic servers.

Actions
Copy link
 #3

Updated by stbuehler over 16 years ago

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

multiple workers just should not be used.

Actions
Copy link

Also available in: Atom