I'd redirect STDERR to a file (and probably do that in a BEGIN block near the top of the main script file).
Using Win32::EventLog in conjunction with a __DIE__ handler would perhaps be a better solution.
When Perl dies, it almost always says something on the way down. I suspect Win32 is just throwing this information away.
Wouldn't a pucker *nix daemon also throw away any parting STDERR output? The done thing is to close all the standard filestreams isn't it?
It's quite likely that (if enabled) any non-zero termination code or STDERR output would end up in the system or application portion of the event log
In reply to Re^2: Debugging Windows Services created with Win32::Daemon (STDERR)
by BrowserUk
in thread Debugging Windows Services created with Win32::Daemon
by hackdaddy
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |