That is simply not true. STDERR is not just for "errors", despite the name. It is also for diagnostic messages, and pretty much anything that should not be considered the "regular ouput" from the application.
I will never vote in favor of allowing any such DEBUG messages (enabled by an environment variable) to be sent to a log file. You could however do it manually by redirecting STDERR (2) to a log file. When that is said: This should never ever be done in production. Doing so adds an overhead that slows down your application. The STDERR constants used through Mojolicous (and other CPAN modules) are simply for developers to get that extra bit of information about what is going on under the hood when nothing else makes sense. I also have no idea why you want this. You ask for something, without explaining what it solves. On Monday, April 6, 2015 at 4:54:21 PM UTC+2, Nathan Waddell wrote: > > Would there be value seen in a patch that allowed a log path to be used as > the value of MOJO_DAEMON_DEBUG? > > MOJO_DAEMON_DEBUG='/var/log/mojo.debug' > > On Monday, April 6, 2015 at 9:49:37 AM UTC-5, Nathan Waddell wrote: >> >> Looking at the source, I do indeed see that it uses warn. >> >> I am deploying hypnotoad as a foreground process being run and monitored >> under a service manager. This service manager is designed along UNIX >> conventions, one of which is that STDERR should be reserved for true >> errors. >> >> I think I could create a warn handler, but I imagine there would still be >> difficulty separating true warns from simple debugging. Is there a >> technique I could employ to work around this? >> > -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
