On Thu, Jan 02, 2003 at 11:27:35PM -0800, Paul Johnson wrote:
> Running sid, why has logcheck started producing this?
>
> /usr/sbin/logcheck: line 107: /bin/egrep: No such file or directory
As others have said, an NMU of grep moved things around. The fix until
a new logcheck is uploaded is to ad
Paul Johnson said:
> Running sid, why has logcheck started producing this?
> /usr/sbin/logcheck: line 107: /bin/egrep: No such file or directory
perhaps something happened to /bin/egrep?
nate
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [E
Paul Johnson wrote:
> Running sid, why has logcheck started producing this?
[snip]
> /usr/sbin/logcheck: line 107: /bin/egrep: No such file or directory
Because with the newest grep package, egrep is now in /usr/bin. It's
logcheck's fault for hard-coding the path. I understand this will be
fixe
On 2003-01-02 23:27, Paul Johnson wrote:
> Running sid, why has logcheck started producing this?
[...]
> /usr/sbin/logcheck: line 107: /bin/egrep: No such file or directory
[...]
There is some devel discussion about it here:
http://lists.debian.org/debian-devel/2003/debian-devel-200301/msg00064.ht
Running sid, why has logcheck started producing this?
- Forwarded message from Cron Daemon <[EMAIL PROTECTED]> -
Received: from root by ursine.dyndns.org with local (Exim 3.36 #1 (Debian))
id 18ULqE-0004O0-00
for <[EMAIL PROTECTED]>; Thu, 02 Jan 2003 23:02:02 -0800
From: [
Hi,
I have been trying to track down a problem with logcheck. I get a
similar error everytime it runs, and it appears it is not creating the
appropiate directory. Any thoughts would be appreicated.
This system is tracking TESTING (sorry woody)
sandbox:/etc/cron.d# dpkg -l logcheck
Desired=Unkn
6 matches
Mail list logo
