>>>>> "Jamie" == Jamie L Penman-Smithson
>>>>> "Re: Bug#311216: logcheck: mails "egrep: Invalid content of \{\}""
>>>>> Mon, 30 May 2005 17:58:30 +0100
Jamie> Hi John,
>> Mail sent by logcheck
>>
>> ,----
>> From: [EMAIL PROTECTED] (Cron Daemon)
>> Subject: Cron <[EMAIL PROTECTED]> if [ -x /usr/sbin/logcheck ]; then
>> nice -n10 /usr/sbin/logcheck; fi
>> To: [EMAIL PROTECTED]
>> Date: Sun, 29 May 2005 18:02:09 -0400 (EDT)
>>
>> egrep: Invalid content of \{\}
>> `----
>>
>> egrep: Invalid content of \{\} `----
Jamie> I can't reproduce this at all, which makes me think there's
Jamie> something different on your system that is causing this
Jamie> bug.
Jamie> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ squid\[[0-9]+\]:
Jamie> WARNING: found whitespace in HTTP header name {Cache
Jamie> Control: no-cache}$
Jamie> With this rule, egrep parses it fine:
Jamie> D: [1117469713] cleanchecked - dir -
/tmp/logcheck.fb7dSc/ignore/spamd
Jamie> D: [1117469713] cleanchecked - dir -
/tmp/logcheck.fb7dSc/ignore/squid
Jamie> D: [1117469714] cleanchecked - dir - /tmp/logcheck.fb7dSc/ignore/ssh
Jamie> However, since there is nothing to lose by escaping the
Jamie> {}'s, I've modified that rule in CVS.
Maybe it just depende upon what you depend upon. :)
A mixed box
$ COLUMNS=200 dpkg -l|egrep 'egrep'
ii grep 2.4.2-3
GNU grep, egrep and fgrep.
$ echo foo|egrep 'name {Cache Control: no-cache}$'
egrep: Invalid content of \{\}
A Sid box
$ COLUMNS=200 dpkg -l|egrep 'egrep'
ii grep 2.5.1.ds1-4
GNU grep, egrep and fgrep
$ echo foo|egrep 'name {Cache Control: no-cache}$'
$
HTH
jam
pgprZ9YuFvY5y.pgp
Description: PGP signature
