in reply to Why does IPC::System::Simple not capture output when Perl is running as CGI under IIS?

Because there is no console allocated, happens under apache too, see Re^5: Win32: Setting a layer with binmode causes problem with close() on Windows (PerlIO silently fails to close the file) for some details

  • Comment on Re: Why does IPC::System::Simple not capture output when Perl is running as CGI under IIS? (console)

Replies are listed 'Best First'.
Re^2: Why does IPC::System::Simple not capture output when Perl is running as CGI under IIS? (console)
by matterofact (Initiate) on Jul 11, 2013 at 16:53 UTC

    So there's no way to work around this using IPC::System::Simple? Should I just revert back to using qx// and forget about it?

[reply]
[d/l]

      So there's no way to work around this using IPC::System::Simple?

      I don't know.

      Should I just revert back to using qx// and forget about it?

      If qx// works, its probably because its creating a console  cmd /x /c ...your stuff here .. as in  C:\WINDOWS\system32\cmd.EXE

      So you might be able to persuade IPC::System::Simple to use the shell (cmd.exe) , but it kind of defeats the purpose of using IPC::System::Simple

      Or you might use Win32::ShellQuote like I showed to launch cmd.exe safely with qx{}

      Or you might make it work if you manage to use Win32::Console to allocate a console

      FWIW, I think the real problem is win32 webservers which spawn procs without an allocated console (IMHO dumb), but I haven't even seen this issue discussed anywhere

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom