Description of problem:

If timing is "right" then whomever gets root messages is 
subjected to messages like "anacron: Cannot run - another
anacron process is already running.: Resource deadlock avoided".
Fine and dandy but really usefulness of such information
is not very high.  This one gets from "Anacron job 'cron.daily'"
and 'cron.weekly' and 'cron.monthly'.

If there is no better way to shut that down then can we
have at least '>/dev/null 2>&1' in corresponding scripts?
Or drop with grep these "deadlock" message to a bitbucket
if /dev/null treatment could remove something really important?

Another option would be a guard in those scripts in this style:

pgrep anacron >/dev/null || anacron -u cron.daily

I guess that an assumption that 'procps' package is present is
quite safe or "type -p pgrep" can be tested before we are trying
to use it. Say

[ "$(type -p pgrep)" ] && pgrep anacron >/dev/null && exit 1
anacron -u cron.daily

or something similar.

Version-Release number of selected component (if applicable):
anacron-2.3-38.FC6