tree 3715e79d53b21ba9819513bdf1e1ca9298e5ca6d
parent 792918c7045d75344a6fadcc872b4c60ad69338b
author showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> 1237582338 +0000
committer showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> 1237582338 +0000

As discussed on the mailing list, we implemented logging with a single
root logger and logging configurations per entry points. The entry
points affected are:

 * Autotest client
 * Autoserv
 * Scheduler

We are sending patches for each one of those entry points. Now we don't
need to 'grab' loggers anymore to log messages, only need to use the
utility functions:

logging.info('msg')
logging.debug('msg')
logging.warning('msg')
logging.error('msg')
logging.critical('msg')

Which reduces complexity of the log system, and makes it easier for
developers to log messages, just select the level, make sure the
standard logging module is loaded, and profit!

From: Lucas Meneghel Rodrigues <lmr@linux.vnet.ibm.com>
Signed-off-by: Steve Howard <showard@google.com>


git-svn-id: http://test.kernel.org/svn/autotest/trunk@2915 592f7852-d20e-0410-864c-8624ca9c26a4