Description of problem:
Logrotate rotates atop's log files, but atop already handles this. Logrotate's renaming of the log files breaks the ability to use 'atop -r YYYYMMDD' to open a past day's data without specifying the path to the rawfile.

Version-Release number of selected component (if applicable):
atop-1.23-8.el5
logrotate-3.7.4-9

How reproducible:
Always.

Steps to Reproduce:
1. Install atop
2. Wait several days for atop's cron job and logrotate to run
  
Actual results:
A series of files like the following in /var/log/atop/.

-rw------- 1 root root        0 Jun 27 04:02 atop_20100626
-rw-r--r-- 1 root root 12592860 Jun 27 00:00 atop_20100626.1
-rw-r--r-- 1 root root 14081677 Jun 27 19:42 atop_20100627

Expected results:
A series of files like the following in /var/log/atop.

-rw-r--r-- 1 root root 12592860 Jun 27 00:00 atop_20100626
-rw-r--r-- 1 root root 14081677 Jun 27 19:42 atop_20100627

Additional info:
Logrotate should completely ignore atop's daily rawfiles at /var/log/atop/atop_* 

/etc/cron.d/atop takes care of rotating and expiring them.