On Wed, 2010-08-18 at 13:33 -0400, Mike Strickland wrote:
> I have had rkhunter set up for some time now to run overnight via cron.
> For about 4 days now, I've been getting an email stating:
>
> Unable to get the lock file: rkhunter has not run!
>
> I have not changed anything, so I'm not sure why this message occurs. If
> I try to run rkhunter in terminal, I get the same message after it
> counts out 300 seconds.
>
This is rkhunter's locking mechanism to prevent 2 or more instances of
RKH running together (and so messing up the log file for a start). By
default it is not enabled, so you must have set USE_LOCKING=1 in the
config file.
To remove the lock file simply run:
rkhunter --unlock
John.
--
John Horne, University of Plymouth, UK
Tel: +44 (0)1752 587287 Fax: +44 (0)1752 587001
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Rkhunter-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rkhunter-users
