On 02/28/2018 04:19 PM, Dave Mitchell wrote:
On Wed, Feb 28, 2018 at 12:31:55PM -0500, Jeffrey Ross wrote:
I got a bunch of perl updates that came down today and they seem to have
caused some problems with exim's script exiqsumm
Use of uninitialized value $ARGV[0] in string eq at /usr/sbin/exiqsumm line 48.
I'm using the following command which kicks the error out "/usr/bin/mailq |
/usr/sbin/exiqsumm".
the line in /usr/sbin/exiqsumm is;
(lines 48 through 53)
if ($ARGV[0] eq '--version') {
print basename($0) . ": $0\n",
"build: 4.90_1\n",
"perl(runtime): $]\n";
exit 0;
}
I'm guessing the error is a warning since the command still runs as
expected.
It's a warning. It seems unlikely that a minor change to a perl version would
cause a change there. The warning is happening because its testing whether
the first command-line argument is equal to '--version', and there is no
first argument ($ARGV[0]).
Has the exiqsumm script also been updated recently? Its possible that a
newer release has enabled warnings (they're not on by default in perl),
either by adding '-w' to the #!/usr/bin/perl first line, or by adding
"use warnings" somewhere near the top of the script.
Looks like the answer is probably yes to both questions
I have a script that runs every 15 minutes that calls /usr/sbin/exiqsumm
and right after I ran "dnf update" and received a bunch of Perl updates
I started getting the warning.
It also looks like I missed the fact that exim was updated via the dnf
command today as well and it does have "use warnings;" at line 44 which
is the first non comment line in the script.
Since this is simply a warning and not a failure I can do one of a few
things
1) ignore the warning which generates an email from cron
2) remove the "use warnings" from the exiqsumm script
3) send standard error for the this cron job to /dev/null
Thanks for the help
Jeff
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
