openerp-scripts: control startup logging level

[Georges Racinet]

It is quite common to want by default one's server to start with logs at level INFO, but some scripts at a higher level.
Otherwise, the DB loading phase (session.open) simply clutters the output for not much benefit.

This is especially annoying in case the openerp script is Sphinx, because any log with level WARNING are interpreted as warnings for the documentation build itself. Of course a warning log is something to care about, but issues must be separated.

Same applies to other scripts, such as nosetests or sometimes custom batch processes : DB loading logs are often not the point, even in the latter case, because they are very probably repeated identically in the neighbouring server log.

We could provide a new option for openerp-scripts to that effect.

An example declaration would be :

   sphinx-build=sphinx-build openerp-log-level=ERROR command-line-options=-d

and that would set the level of the 'openerp' logger to ERROR before the database opening. Of course, the actual script may very well reset it afterwards to whatever value is considered appropriate for its processing.

The combination with '-d' is the more interesting, since '-d' is meant for scripts (such as Sphinx) which have no knowledge of OpenERP at all : the loading occurs before the true beginning of the script.

[Georges Racinet (gracinet)]

Since maturation of 1.9.0 may be a bit long, this one could be a candidate for backport to the 1.8 branch.
Done in trunk to allow for change if there are some suggestions in the near future.