On 28 February 2018 at 22:17, Chris Adams wrote:
> Once upon a time, Jeffrey Ross said:
>> 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)
Once upon a time, Jeffrey Ross said:
> 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
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
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 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/ma
