Dear Logcheck List Member,<br><br><div class="gmail_quote">
I am Laszlo Toth an interested person in Logcheck usage. My intention is to use Logcheck for analysing firstly a Cisco PIX and MS IIS 6.0 log files right after when I will see the result I would like to build a more advanced system for the log analysis.<br>
<br>Actually I have two problems I need to solve.<br>1st<br>The cron daemon send me a system in every hours which contains the following error message:<br>
<br>
Subject: Cron <logcheck@san> logcheck if [-x /usr/sbin/logcheck ];<br>
then nice -10 /usr/sbin/logcheck; fi<br>
Content:<br>
/bin/sh -c: line 0: syntax error near unexpected token 'then'<br>
/bin/sh -c: line 0: logcheck if [-x /usr/sbin/logcheck ]; then nice<br>
-10 /usr/sbin/logcheck fi<br>
<br>
I have a Debian lenny beta version. My related environment variables are the following (can be found in the error message):<br>
X-Cron-Env:<PATH= /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin><br>
X-Cron-Env: <SHELL= /bin/sh> -> bash<br>
<br>
What is the source of the mentioned problem and how I can get this resolved?<br>
<br>2nd<br>I mentioned that I would like to analyse web & firewall logs more after the log made. For example I will analyse log files made on 2008-01-01 10:12:00 tomorrow. On every single row Logcheck made an error message: "line has bad date" What is the reason for writing that remark to the outpu file? How can I avoid being the situation like this?<br>
<br>I have already attempted that I gave the date when the log file was made. For example in the logcheck.configure "DATE="2008-01-01 10:12:00". That was ineffective to the "line has bad date" error message. What shall I do? Thank you for you answer.<br>
--<br>
<font color="#888888">Laszlo Toth<br>
</font></div>