|
From: Graziano <dre...@li...> - 2010-04-01 22:41:19
|
to fix the issue I was forced to remove this part of code from
reloadConfigFile
if ( $Config{$name} ne $newConfig{$name} ) {
if ( $newConfig{$name} =~ /$valid/i ) {
my $new = $1;
my $info;
if ($onchange) {
$info = $onchange->( $name, $Config{$name}, $new );
} else {
mlog( 0,
"AdminUpdate: $name changed from '$Config{$name}' to '$new'"
);
${$name} = $new;
# -- this sets the variable name with the same name as the config key to
the new value
# -- for example $Config{myName}="ASSP-nospam" -> $myName="ASSP-nospam";
}
$Config{$name} = $new;
} else {
mlog( 0,
"AdminUpdate:error: invalid '$newConfig{$name}' -- not changed"
);
}
}
> I have a big issue with 1.7.1 .
>
> Several clients are reporting that randomly ASSP executes a
> Apr-01-10 21:57:01 Reloading config;
>
> after this Reloading config ASSP loads all values in assp.cfg.defaults
>
> Apr-01-10 21:57:01 AdminUpdate: bombDataReMaxHits changed from '2' to '';
> Apr-01-10 21:57:01 AdminUpdate: bombReISPIP changed from '1' to '';
> Apr-01-10 21:57:01 AdminUpdate: bombMaxPenaltyVal changed from '70' to '';
> Apr-01-10 21:57:01 AdminUpdate: maxBombSearchTime changed from '5' to '';
> and so on ...
>
> it fully mess up smtp setting and ASSP simply stop to work ...
> How to prevent "Reloading config" ?
>
> Graziano
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Assp-test mailing list
> Ass...@li...
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
|