Olivier Berger wrote:
Package: sympa
Version: 5.2.3-1
Severity: minor
Tags: patch
Sympa logs (/var/log/sympa.log) contain error messages complaining for file
/style.css not found :
could not find CSS file /style.css, using default CSS
Such error occurs all the time (each action in wws, acutally), and thus
annoying. I noticed it by using logcheck.
But I think this is actually no error when no css_path was defined (by
default), according to the docs, because in such case, sympa will construct a
dynamic CSS instead of using a predefined static CSS file (css_path + css_url).
So this should only be an info message I think, when no css_path is defined (or
nothing).
You're right it may be a common behavior and users should not get these
logs.
We've make things better in current development version where :
* a new static_content/ directory has been added to store all these
contents (like CSS, SOAP WSDP, user pictures, ...) that don't
change and therefore don't require any wwsympa processing.
* CSS is automatically updated (in static_content/ directory) after
an upgrade process
* As a consequence, Sympa no more fills out his logs with the
message you report
But we don't have plans to report all these changes to 5.2.x branch.
Here's a proposed workaround.
/usr/lib/cgi-bin/sympa# diff -uibw wwsympa.fcgi.orig wwsympa.fcgi
--- wwsympa.fcgi.orig 2007-01-23 14:52:04.000000000 +0100
+++ wwsympa.fcgi 2007-01-23 14:49:20.000000000 +0100
@@ -723,7 +723,7 @@
$param->{'css_url'} = &Conf::get_robot_conf($robot, 'css_url');
## If CSS file not found, let Sympa do the job...
unless (-f $param->{'css_path'}.'/style.css') {
- &wwslog('err','Could not find CSS file %s, using default CSS',
$param->{'css_path'}.'/style.css');
+ &wwslog('info','Could not find CSS file %s, using default CSS',
$param->{'css_path'}.'/style.css');
$param->{'css_url'} = $param->{'base_url'}.$param->{'path_cgi'}.'/css';
}
In fact, I think a better algorithm should be needed : if no css_path is
defined, nothing to log, and otherwise, if the file is not found in css_path,
then THERE is an error to log, then.
Hope this helps.
Should probably be forwarded upstream ?
