Package: grep
Version: 2.5.4-4
Severity: normal
egrep -f takes its input from a file. This functionality is often used
i.e. with logcheck, which works basically off a directory full of
files which contain regexes representing log messages to be either
ignored or pushed up - However, when something goes bad and one of
those lines is not parsable, grep won't help in debugging. As an
example, I got loads of log messages such as:
From: Cron Daemon <[email protected]>
To: [email protected]
Date: Tue, 21 Apr 2009 23:02:02 -0500 (CDT)
Subject: Cron <logch...@lafa> if [ -x /usr/sbin/logcheck ]; then nice
-n10 /usr/sbin/logcheck; fi
egrep: Unmatched [ or [^
Finding the file/line where I made this particular mistake was a
tedious job. Users deserve egrep to report the filename and line
number where this error happened.
Thanks,
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-vserver-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages grep depends on:
ii libc6 2.9-7 GNU C Library: Shared libraries
grep recommends no packages.
Versions of packages grep suggests:
ii libpcre3 7.8-2 Perl 5 Compatible Regular Expressi
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
