From: Horms Subject: [PATCH] xend: log process id Date: Wed, 28 Jun 2006 11:02:29 +0900 Message-ID: <20060628020227.GA28692@verge.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel List-Id: xen-devel@lists.xenproject.org Have the parent id logged in the log file, this is very useful when debugging xend as it has multiple processes, and it can be hard to work out which one is doing what without this information. Signed-Off-By: Horms diff -r 71a0b1d230c1 -r 2cd7f2c1744a tools/python/xen/xend/XendLogging.py --- a/tools/python/xen/xend/XendLogging.py Thu Dec 1 09:37:58 2005 +++ b/tools/python/xen/xend/XendLogging.py Thu Dec 1 09:39:39 2005 @@ -42,7 +42,7 @@ DEFAULT_BACKUP_COUNT = 5 STDERR_FORMAT = "[%(name)s] %(levelname)s (%(module)s:%(lineno)d) %(message)s" -LOGFILE_FORMAT = "[%(asctime)s %(name)s] %(levelname)s (%(module)s:%(lineno)d) %(message)s" +LOGFILE_FORMAT = "[%(asctime)s %(name)s %(process)d] %(levelname)s (%(module)s:%(lineno)d) %(message)s" DATE_FORMAT = "%Y-%m-%d %H:%M:%S"