Package: grep
Version: 2.5.1.ds1-6
Severity: normal
Today, I updated grep.
After that I found that grep, which is called from my .procmailrc, was
hogging the cpu.
A look at the procmail.log showed:
procmail: Forcing lock on "blacklist.lock"
procmail: Forcing lock on "blacklist.lock"
procmail: Forcing lock on "blacklist.lock"
procmail: Timeout, terminating " $FORMAIL -x from: -x sender: | $GREP -iqFwf
$BLACKLIST"
And yes, top and ps showed a lot of exactly these grep processes hogging the
CPU.
I examined the $BLACKLIST file and found it to be unchanged from it's
October 2004 content. It contained exactly one byte. I guess a <CR>.
I removed the file and recreated it with touch and didn't get any
problems with grep after that.
The old package from testing did not expose that behaviour, so I guess
one of these must be the culprit:
* 64-egf-speedup.patch, 65-dfa-optional.patch, 66-match_icase.patch,
67-w.patch speed up grep. Thanks to Nicolas François
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13-rc6-git3
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages grep depends on:
ii libc6 2.3.5-6 GNU C Library: Shared libraries an
grep recommends no packages.
-- no debconf information
