Bugzilla – Bug 9459
Redefined strings - increase logging level to Info
Last modified: 2009-07-31 10:29:48 UTC
I can't see why these need to be logged at the Warn level. (Although I have no idea which log setting controls these log entries, I see them when nothing is set higher than Warn).
Andy, care to chime in on this
Do you mean standard Perl warnings? Those aren't controlled by the log settings.
Created attachment 4050 [details] beginning of server.log at startup (In reply to comment #2) > Do you mean standard Perl warnings? Those aren't controlled by the log > settings. I'm not sure I understand what you're asking. See the attached log. Are these standard Perl warnings? I have a custom-strings.txt file and each time SquezeCenter is started every string that's redefined gets logged in the server.log. String redefinition seems like a fairly basic thing and it all works as expected, so I don't see the need to log them at the default logging levels.
My apologies for being a lazy***. Here's the code from Utils::Strings::storeString() : if (defined $strings->{$currentLang}->{$name} && defined $curString->{$currentLang} && $strings->{$currentLang}->{$name} ne $curString->{$currentLang}) { $log->warn("redefined string: $name in $file"); } So it would be a matter of changing this to info or debug if you agree that it should be raised.
change 23462
This bug has been fixed in the 7.3.0 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Reduce number of active targets for SC