amstatus is reporting all kinds of unitialized value errors, which since I have
cron job that runs amstatus regularly to determine if a wake on lan is needed on
clients that might be being backed up, I get tons of log spam (since every run
of amstatus results in errors such as the ones below).
I'm not sure yet of the actual impace of these errors.
** (process:16121): WARNING **: Use of uninitialized value in numeric ne (!=) at /usr/sbin/amstatus line 407, <AMDUMP> line 2452.
** (process:16121): WARNING **: Use of uninitialized value in numeric eq (==) at /usr/sbin/amstatus line 407, <AMDUMP> line 2452.
** (process:16121): WARNING **: Use of uninitialized value in numeric ne (!=) at /usr/sbin/amstatus line 407, <AMDUMP> line 2461.
** (process:16121): WARNING **: Use of uninitialized value in numeric eq (==) at /usr/sbin/amstatus line 407, <AMDUMP> line 2461.
** (process:16121): WARNING **: Use of uninitialized value in numeric ne (!=) at /usr/sbin/amstatus line 407, <AMDUMP> line 2470.
** (process:16121): WARNING **: Use of uninitialized value in numeric eq (==) at /usr/sbin/amstatus line 407, <AMDUMP> line 2470.