comment on

If you want to see the output of the text, your best option is the Pipe.
Ironicly i just asked rfp for some advice about his 'Pesky Pipe' problem so i can give you the example script and output:


[root@wicca /root]# cat ppipe.pl
#!/usr/bin/perl

open(FILE,"/bin/netstat|") || die("can't open");
while(<FILE>){
        print $_;
}
close(FILE);


[root@wicca /root]# perl ppipe.pl
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         St
+ate
tcp        0      0 10.9.205.4:netbios-ssn  aeon-gig:1028        ESTAB
+LISHED
tcp        0      0 10.9.205.4:ssh          aeon-gig:4931        ESTAB
+LISHED
Active UNIX domain sockets (w/o servers)
Proto RefCnt Flags       Type       State         I-Node Path
unix  5      [ ]         DGRAM                    644    /dev/log
unix  2      [ ]         DGRAM                    1512
unix  2      [ ]         DGRAM                    1504
unix  2      [ ]         DGRAM                    904
[root@wicca /root]#
[download]

In reply to Re: executing commands and getting output by gilbert0
in thread executing commands and getting output by tja_ariani

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl-Sensitive Sunglasses
	PerlMonks