[Solved] bad acces log not trapped

Added by lighthouse over 13 years ago

I made a typo in my config and gave invalid path for error log and acces log files.

when I started lighttpd it failed with an clear message on the error log mistake but having corrected that it failed to flag the mistake on the access log, It just failed to start.

If I had not made the first error I would have wasted a lot of time before finding the second one.

Should be trapped,


Replies (1)

RE: [Solved] bad acces log not trapped - Added by gstrauss about 2 years ago

For a long time now, lighttpd issues trace if it fails to open the accesslog file.