On 10/28/2011 02:16 PM, Pierre Riteau wrote:
Yes, it would be better if we could have error output on stderr. Now,
"simple" errors such as a missing image file (or wrong path to the
image) are reported to syslog instead. It could be the source of some
headaches...
Is there a way we could have the child send the error to the parent
over a pipe and have the parent print it on stderr?
A way could be to change the fork() into a separate thread, so that you
can daemonize as soon as you accept the socket rather than having to do
it early.
Paolo
