in reply to Re^2: How do I communicate with a Windows process?
in thread How do I communicate with a Windows process?

Is it safe to say "Stay away from the Win32:: namespace!" is a good idea?

Hell no! There are lots of not just useful, but in many cases little-alternative-to, modules in there.

It just pays to look for the simplest solution first.

BTW: Does this also work for you? (If not, why not?): 

my @info = qx[ netstat -a -e -n -o -s -r ];;
print for @info;;

[download]
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP an inspiration; A true Folk's Guy

Replies are listed 'Best First'.
Re^4: How do I communicate with a Windows process?
by IOl01 (Novice) on Jul 26, 2010 at 04:06 UTC

    Umm… I was a little premature in saying my @info = `start /b /wait netstat -a -e -n -o -s -r`; works.

    I am trying to display the output of netstat on a web page. Whenever the CGI script is hit, a command window briefly flickers into existence then closes as the netstat command completes (and this is with BrowserUK's suggestion in place).

    The Fine Print:
    Before I get jumped on for the security issues, Apache is set up to only serve this CGI script to the local network (and the network is physically disconnected from the rest of the world).

[reply]

      So, the "brief flicker" of a command window on the screen of an internal web-server is problem?

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
        you can always start it minimized :)
        help start
start /min .....

        [download]
[reply]
[d/l]

In Section Seekers of Perl Wisdom