Received Sat 19 Feb 2005 8:39am +1100 from Reuben Thomas:
> Package: wajig
> Version: 2.0.22
> Followup-For: Bug #288852
>
> I too have observed this behaviour. The problem is that wajig is
> running grep under my default locale (en_GB.UTF-8 in my case) which is
> much slower than grep in C locale. This is arguably a grep bug, but
> the practical upshot is that wajig needlessly hogs the CPU.
>
> An example command under which this happens is wajig daily-upgrade,
> which is one of the commands I use most frequently, so it's
> particularly annoying.
>
> Rather than blanket-setting the locale as it did before, perhaps wajig
> could specifically set the C locale before running sub-commands where
> a) it doens't matter (from a locale point of view) and b) the program
> being run is much slower under a non-8-bit locale. grep is in fact the
> only such command that springs immediately to mind.
Okay. I do have the framework in place for doing this. But I use a
lot of greps! Anyhow, in /usr/share/wajig/changes.py I have changed
line 172 from
perform.execute(command, noquiet=True) # root is not required.
to
perform.execute(command, noquiet=True, langC=True) # root is not required.
This is where the specific grep command you mention is called
(daily-upgrade). If you are able to test this (i.e., you have access
to root and can make this one change in your installed wajig) and
confirm it fixes your problem that would be most appreciated.
Regards,
Graham
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
