MS Slow after update to 4.50.14 on suse

Julian Field MailScanner at
Fri Feb 3 10:04:42 GMT 2006


On 3 Feb 2006, at 09:49, Glenn Steen wrote:

> On 03/02/06, Julian Field <MailScanner at> wrote:
>> On 2 Feb 2006, at 22:05, Glenn Steen wrote:
>>> On 02/02/06, Scott Silva <ssilva at> wrote:
>>>> Glenn Steen spake the following on 2/2/2006 1:05 PM:
>>>>> On 02/02/06, Scott Silva <ssilva at> wrote:
>>> (snip)
>>>>>> One problem I see is either an old or no file
>>>>>> /etc/MailScanner/reports/en/languages.conf. See if this is
>>>>>> either a 0 length
>>>>>> file, or if you have a /etc/MailScanner/reports/en/
>>>>>> languages.conf.rpmnew file.
>>>>> Ah yes. I actually (he said blushing) walked into that myself this
>>>>> time around... Silly cut'n'paste all the three lines... Oh  
>>>>> well, if
>>>>> that is it, it¨s just a matter of moving languages.old back into
>>>>> place...
>>>>> Jules, perhaps you should stress the need to look for an rpmnew  
>>>>> file
>>>>> first, before blithely doing the upgrade(s)?... In the nice usage
>>>>> would be a good place...
>>>>> --
>>>>> -- Glenn
>>>>> email: glenn < dot > steen < at > gmail < dot > com
>>>>> work: glenn < dot > steen < at > ap1 < dot > se
>>>> I thought Julian had fixed the upgrade_languages_conf to not do
>>>> this a few
>>>> months ago. Maybe my rememberer is busted...
>>>> I usually check, now, after being bitten by this one.
>>> If so, he managed to un-fix it to this version:-). If you cu'n'oaste
>>> the suggested lines to do the upgrade the first one creates the
>>> zero.length file, and the subsequent move move it into place...
>>> Empirical study (meaning: I goofed up:) show that it certainly will
>>> behave as I describe;)
>> Check you upgrade_MailScanner_conf or upgrade_languages_conf (one is
>> a link to the other) for this code
>> Usage() unless $oldfname &&    $newfname &&
>>              -f $oldfname && -f $newfname &&
>>              -s $oldfname && -s $newfname;
>> That really should do the job.
> :-)
> Not really... The instructions are the in the Usage itself:
> --------------------
> ===
> If you are using the RPM distributions then try this:
> cd /etc/MailScanner/reports/en
> upgrade_languages_conf languages.conf languages.conf.rpmnew >  
> mv -f languages.conf languages.old
> mv -f  languages.conf
> ---------------------
> Now, the upgrade thing behaves exactly right, BUT you still create a
> zero-lenght file because the Usage is printed to STDERR, and _nothing_
> to STDOUT. Sure, it's pretty obvious whatwith the Usage carooming by
> on the screen, but still... If you try to make all this "unattended"
> or is a bit preoccupied with other things (that'd be me:-) it just
> _might_ slip by (not that I did let that happen, mind you:-).
> Note that this is singularly for when you do a cut'n'paste _from the
> Usage itself_. So having a few words about _not doing it if there's no
> rpmnew file_ might be a good idea. Specifically since this tend to
> crop up from time to time:-).

So if the Usage is printed, I need to cat the incoming file to stdout  
as well. Will that fix it? I'm not sure I 100% understand you if that  
is not right.

- -- 
Julian Field
Buy the MailScanner book at
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654

Version: PGP Desktop 9.0.4 (Build 4042)


This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

More information about the MailScanner mailing list