I am pretty sure debug output went to apache's error log when I last checked.
On Mon, Jan 18, 2010 at 8:54 PM, Adam Mackler <[email protected]> wrote: > Hi Toby: > > The output might be going to your web server log. Try starting your > fastcgi script with a -e option (with CATALYST_DEBUG set as well). > > Adam > > On Mon, Jan 18, 2010 at 05:03:23PM +1100, Toby Corkindale wrote: >> Hi guys, >> If you're running a Catalyst app with the fastcgi script (as found in >> scripts/myapp_name_fastcgi.pl), then is there a way to enable the debug >> mode. (eg. like running scripts/myapp_server.pl -d) >> >> I've tried setting CATALYST_DEBUG and MYAPP_DEBUG in the shell >> environment, but that doesn't seem to work. Either that or else fastcgi >> is discarding the output somewhere in our case. (I've messed with the >> -keeperr option too) >> >> Cheers, >> Toby >> >> _______________________________________________ >> List: [email protected] >> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst >> Searchable archive: http://www.mail-archive.com/[email protected]/ >> Dev site: http://dev.catalyst.perl.org/ > > _______________________________________________ > List: [email protected] > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: http://www.mail-archive.com/[email protected]/ > Dev site: http://dev.catalyst.perl.org/ > -- David Schmidt | http://www.fm5.at _______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
