Linux + exit status from Perl one-liner code

kshlinuxperl

I use Perl one-liners in my ksh scripts.

Sometimes it's necessary to get an exit status from the Perl one-liner in order to verify if the Perl one-liner succeeded or not.

For example, I need to verify if the "print" in the Perl one-liner code succeeded or not.

But Perl will exit with status 0 in both cases even if Perl does not match the words "AAA and BBB".

Maybe by changing my code I can get exit status 0 when Perl matches successfully. And get exit status 1 when Perl does not match the words "AAA and BBB".

Is this possible?

more file
AAA BBB


perl -ne '/AAA/ && /BBB/ && print' file
AAA BBB

echo $?
0

more file1
ZZZ

perl -ne '/AAA/ && /BBB/ && print' file1
echo $?
 0

Best Answer

Count matching lines and set exit code based on it in an END{...} block:

perl -ne '/AAA/ && /BBB/ && print && $MATCH++; END{exit 1 unless $MATCH>0}' file

Related Solutions

Perl in place edit within a script

do {
  local $^I='.bak'; # see perlvar(1)
  local @ARGV=("file");
  while(<>){
    s/<value>/<value>/ig;
    print;
  }
};

Beware though: $^I like perl's -i isn't crashproof.

Exit code 13 from Perl’s system() command

It would help to see some of your code/output. Here's my guess at the root cause of your problem.

First, signal 13 equates to SIGPIPE, which in this case seems to indicates the perl process is attempting to write to a pipe (i.e. STDOUT/STDERR), but nothing is there to read it.

I tested a bit and my question is, are you handling the output from the the script within your C program? In my tests, simply processing the output of the perl script avoided the SIGPIPE error.

Signal 13 produced:

fp = popen("/home/chuckx/perl-test/perl.pl","r");
status = pclose(fp);

Signal 13 avoided:

fp = popen("/home/chuckx/perl-test/perl.pl","r");

do {} while (fgets(output,80,fp) != NULL);

status = pclose(fp);

Best Answer

Related Solutions

Perl in place edit within a script

Exit code 13 from Perl’s system() command

Related Topic