What is the difference between launching `script/myapp_fastcgi.pl -daemon` and running `nohup script/myapp_fastcgi.pl &' ?
I want to be able to run fastcgi.pl -l in the background, with debugging enabled, and log its STDERR. I tried script/myapp_fastcgi.pl -l 127.0.0.1:55900 -d 2>>myapp.stderr but only the initial startup screen ended up in myapp.stderr. No debug information about requests was written to the file. Running the same application like this: script/myapp_fastcgi.pl -l 127.0.0.1:55900 2>>myapp.stderr & Works as expected. Even after I log out (without running nohup), the app correctly logs requests to myapp.stderr. I'm writing a tutorial on Catalyst deployment with lighttpd and fastcgi at http://catwiki.toeat.com/gettingstarted/howtos/deploy/lighttpd_fastcgi (please feel free to amend) and want to get a good understanding of this issue. Thanks, Dan _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
