Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

I got two questions, please see here:)

by wildnature (Novice)
on Feb 18, 2011 at 03:53 UTC ( #888839=perlquestion: print w/replies, xml ) Need Help??

wildnature has asked for the wisdom of the Perl Monks concerning the following question:

Q1:If I press Ctrl+Z or Ctrl+C to stop a perl script, how can I do some flush thing after I press them.

Q2:I execute some command in perl script using `` like `ipconfig`, when the script is running, displays of command "ipconfig" also appears in perl output, how can I just use these command while there is no output displayed?

thanks a lot :)

Replies are listed 'Best First'.
Re: I got two questions, please see here:)
by atcroft (Abbot) on Feb 18, 2011 at 04:07 UTC

    For both questions, I would suggest reviewing perlipc, the perl documentation on inter-process communications. The section on signal handling mentions both Ctrl-C and Ctrl-Z (from question 1), while the section "Using open() for IPC" would be a good place to start for question 2.

    Hope that helps.

    Update: (2011-02-17)

    For reference, I believe (after a quick search) that Ctrl-C sends SIGINT (INT), and Ctrl-Z sends SIGTSTP (TSTP).

    Update: (2011-02-17)

    The example from the section on signal handling can be modified as follows to illustrate handling the INT and TSTP signals:

    A modification of the second code example in the section mentioned for question two uses open() to retrieve interface IP information using the ifconfig command:

Re: I got two questions, please see here:)
by Khen1950fx (Canon) on Feb 18, 2011 at 06:05 UTC
    To suppress output of the command, use the capture method from IPC::System::Simple. The capture command replaces the backticks. For example:
    #!/usr/bin/perl use strict; use warnings; use IPC::System::Simple qw(capture); my @output = capture("ls", "/root/Desktop");
    The output's there just not printed to output. To retrieve the results:
    #!/usr/bin/perl use strict; use warnings; use IPC::System::Simple qw(capture); my @output = capture("ls", "/root/Desktop"); print @output, "\n";

      I tried this method, but it doesn't work

       capture ("dumpcap -i eth0")

      It still print the output :(

Re: I got two questions, please see here:)
by DrHyde (Prior) on Feb 18, 2011 at 10:42 UTC
    1. You'll get better responses if you give your posts a descriptive title. If you have two seperate questions, post them seperately so both can have a good title.
    2. See %SIG in perlvar
    3. You can redirect their STDOUT and STDERR when you shell out to them in the same way as you would in the shell, or you can capture them using backticks or open
      I have to agree with this - you should split your questions and use meaningful titles for the benefit of other users who will likely one day want to do a search when they encounter a similar issue than you.

      There is way more value in acting in the interest of everyone at the monastery than just getting a question answered for yourself.

        Yes, I agree with all of you.

        Sorry for not clear about my titles, I will do better:)

        Thank you all guys :)

Re: I got two questions, please see here:)
by cdarke (Prior) on Feb 18, 2011 at 09:36 UTC
    If I press Ctrl+Z or Ctrl+C to stop a perl script

    Presumably you are running on UNIX or Linux? Please confirm. On those platforms CTRL+Z does not usually stop a process but places it suspended in the background. Depending on the shell you are using, type jobs and you will see a list of them. The shell built-in fg will resume the background process in the foreground. Read the man pages for your shell.

    Both these signals (see above) can be assigned to other keys using stty(1). So if someone has been playfull with your terminal settings they could do almost anything.

    You can trap most signals and execute a signal handler subroutine in most languages (even korn shell and bash: see the trap builtin). For Perl see %SIG in perlvar.
      Looks like Windows. He mentioned ipconfig.
Re: I got two questions, please see here:)
by sundialsvc4 (Abbot) on Feb 18, 2011 at 14:46 UTC

    Piping command-output to “the bit-bucket” (/dev/null on a Unix box) is also useful, with Perl and otherwise.   Both the STDOUT and the STDERR streams can be piped into oblivion in this way.   This notion really isn’t Perl-specific at all:   it’s general shell-scripting practice.

Re: I got two questions, please see here:)
by Anonymous Monk on Feb 18, 2011 at 13:56 UTC

    For Q1, %SIG is the answer, as noted above.

    For Q2, it depends on what you need to do. If you don't need the command output you can just redirect the output to /dev/null. Backticks, or qx//, shouldn't print anything to STDOUT, so maybe you're getting some of hte progam STDERR instead. You can try to execute the command as my @output = `$command 2>&1`, or go to IPC::Open2 or IPC::Open3 if you need to parse the output.

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: perlquestion [id://888839]
Approved by chrestomanci
Front-paged by DrHyde
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others having an uproarious good time at the Monastery: (5)
As of 2022-06-27 23:25 GMT
Find Nodes?
    Voting Booth?
    My most frequent journeys are powered by:

    Results (89 votes). Check out past polls.