Lighty should not crash if it could not write a log file
Lighty crashes, with no error message at all (not even with an entry in its main error log file), if it could not write one access log file.So this is a double problem:
- It should not crash if it could not write an access log file; it may be acceptable if it didn't have write permission on startup, but never if the permissions change after the server started (I would expect the problem to be reported in the main error log file).
- It doesn't provide a useful message to debug the problem; it actually doesn't provide anything at all.
This is the output when one access log file is not writable:
treasure ~: sudo lighttpd -Df /etc/lighttpd/lighttpd.conf treasure ~: echo $? 255
So you can only spot this problem with strace:
strace lighttpd -Df /etc/lighttpd/lighttpd.conf
Also available in: Atom