On Fri, 2007-11-23 at 14:23 -0500, Verdon Vaillancourt wrote: > >> For the last two days, I've been getting many many lines like the > >> following in the email from my daily cron for rkhunter > >> > >> grep: writing output: Broken pipe > >> grep: writing output: Broken pipe > >> grep: writing output: Broken pipe > >> ... and so on ... > >> > >> I'm not entirely sure what may have changed. I know cron itself was > >> updated, but I don't think that's it. I'm not sure where to start > >> looking. Any help would be appreciated. > >> > > The log file (/var/log/rkhunter.log) may indicate what part of RKH is > > failing - that is, which test it is trying to perform. If you have > > trouble working out what is going wrong, then mail me the log file and > > I'll take a look. > > I appreciate the offer. I went to look at the log, and as I had run > rkhunter -V and rkhunter --update this morning, last nights log from > the cron run was lost. > Okay. Don't forget that when RKH runs it renames the previous 'rkhunter.log' to 'rkhunter.log.old'. Additionally you can use the '--nolog' or '--appendlog' options when testing, to ensure that you don't lose any previous log contents.
John. -- --------------------------------------------------------------- John Horne, University of Plymouth, UK Tel: +44 (0)1752 233914 E-mail: [EMAIL PROTECTED] Fax: +44 (0)1752 233839 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Rkhunter-users mailing list Rkhunter-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkhunter-users
