On Wed, 2007-01-03 at 09:41 +0100, Andreas Fassl wrote: > Hello, > > when I try to update rkhunter via cronjob anythings fine. > The option --quiet doesn't remove the output, the adding of --cronjob > leads into > # rkhunter --update --cronjob > Yup, already fixed in the next release.
The use of '-quiet' assumes that the user will check the return code of RKH to determine if there was a problem or not. (Again, this doesn't work too well with the current version, but works better at least for the next release.) Additionally, in your case using --update and --cronjob together, the '-update' will be performed first to ensure the latest files are being used. The current release does it the other wrong way round - the system check first and then it updates the files. John. -- --------------------------------------------------------------- John Horne, University of Plymouth, UK Tel: +44 (0)1752 233914 E-mail: [EMAIL PROTECTED] Fax: +44 (0)1752 233839 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Rkhunter-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rkhunter-users
