search

rdmenezes / remote-testbed

Automatically exported from code.google.com/p/remote-testbed
0 stars 1 forks source link

Improve logging infrastructure #22

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The logging infrastructure should be enhanced based on ideas presented in
the logging enhancement proposal[1]. Should make it easier to filter log
messages and route them to syslog if required.

[1] http://code.google.com/p/remote-testbed/wiki/LoggingEnhancementProposal

Original issue reported on code.google.com by jonas.fonseca on 14 Nov 2007 at 9:08

GoogleCodeExporter commented 9 years ago 
Preliminary patch that adds a static Log class with debug, info, etc. methods 
and
uses it in the diku_mch part of the code.

Original comment by jonas.fonseca on 14 Nov 2007 at 9:12

Attachments:

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago

Original comment by jonas.fonseca on 22 Nov 2007 at 12:23

GoogleCodeExporter commented 9 years ago 
An updated version of the patch.

Original comment by jonas.fonseca on 28 Nov 2007 at 3:14

Attachments:

GoogleCodeExporter commented 9 years ago 
The patch has been integrated and moving MCH to the new logging infrastructure
including cleaning up the log messages has been completed.

Attached is a suggestion to enable syslog when running MCH in daemon mode.

Original comment by jonas.fonseca on 9 Mar 2008 at 12:19

Attachments:

GoogleCodeExporter commented 9 years ago 
The syslog patch has been applied in commit 
c76efc16bc4a56e68245029ac4a10fdde4cda6a1.

Reschedule this issue for 2.0 where MCS should be converted to use the new 
logging
infrastructure.

Original comment by jonas.fonseca on 10 Mar 2008 at 10:51

GoogleCodeExporter commented 9 years ago 
Fixed in commit 267ed2bc36ea22916f7d24e35f0f99bd091f14bf: Issue 22: Convert 
remaining
code to use the log module.

Original comment by jonas.fonseca on 4 Jun 2008 at 2:14