On Mon, 4 Jun 2001, Alvin Oga wrote:
>
> hi ya jiji
>
> > - rebooted which should take care of cron / syslogd / logcheck.sh not
> > running
> > - apt-get --reinstall install logcheck just in case
> > - hacker? that is my fear. How can I find evidence that the @#$@ is in
> > there?
You ma
hi ya francois
my log check sends me an hourly status ... ( its the default log files )
c ya
alvin
On Mon, 4 Jun 2001, Francois Gouget wrote:
> On Mon, 4 Jun 2001, Alvin Oga wrote:
>
> >
> > hi ya jiji
> >
> > > - rebooted which should take care of cron / syslogd / logcheck.sh not
> > > ru
- rebooted which should take care of cron / syslogd / logcheck.sh not running
- apt-get --reinstall install logcheck just in case
- hacker? that is my fear. How can I find evidence that the @#$@ is in there?
On Mon, Jun 04, 2001 at 03:24:05PM -0700, Alvin Oga wrote:
>
> hi jiji
>
> you probabl
hi ya jiji
> - rebooted which should take care of cron / syslogd / logcheck.sh not running
> - apt-get --reinstall install logcheck just in case
> - hacker? that is my fear. How can I find evidence that the @#$@ is in there?
-- what changed since the last time logcheck was working...
-
On Tue, Jun 05, 2001 at 07:58:50AM -0500, hanasaki wrote:
> I have added the following else statement to the script
> so there is always a report. I would appreciate it if the utility's owner
> would
> consider adding this to his/her next revision and giving a small credit if
> they do.
I would
I am running potato with logcheck, for several months. For the last couple of
days there have been some gaps. By this, I mean, logcheck, as installed runs
as a cron job every hour. In the past it has always sent an email, even if
there was nothing to report. Now some hours have no emails bei
Although hackers are still not ruled out, I may have found the problem.
There were some things added, by me, to the .ignore config file.
This has, most likely, resulted in some runs of logcheck.sh not finding
anything to report. Looking at the logcheck.sh script in more detail,
it looks as if
hi jiji
you probably have a problem with:
- check cron ( restart it even if its running
- check syslogd ( restart it even if its running
- run logcheck.sh manually and see if than reports your status
since the last time
- what happend since the June 1st.
Am 05. Jun, 2001 schwäzte Dave Sherohman so:
> On Tue, Jun 05, 2001 at 07:58:50AM -0500, hanasaki wrote:
>
> > I have added the following else statement to the script so there is
> > always a report. I would appreciate it if the utility's owner would
> > consider adding this to his/her next revis
9 matches
Mail list logo
