Worked like a charm. Never realized that my version of logcheck was utilizing the paranoid ignores. There are a couple other entries in the file that have the path in them, but my routine messages don't seem to hit them -or they are still being logged with the path.
The change in the 1st line in the /etc/logcheck/ ignore. d.paranoid/ cron file took care of my problem. I changed it from:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ /USR/SBIN/ CRON\[[ 0-9]+\] : \([_[:alnum:]-]+\) CMD \(.*\)$
to
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ CRON\[[0-9]+\]: \([_[:alnum:]-]+\) CMD \(.*\)$
Worked like a charm. Never realized that my version of logcheck was utilizing the paranoid ignores. There are a couple other entries in the file that have the path in them, but my routine messages don't seem to hit them -or they are still being logged with the path.