From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Smith Subject: Re: Re: [Xen-changelog] Rewritten XendLogging to not be a singleton class, and not have methods used Date: Mon, 10 Oct 2005 10:22:35 -0700 Message-ID: <87br1xmgmc.fsf@us.ibm.com> References: <1128960126.2826.15.camel@bree.local.net> <20051010161625.GB20935@uk.xensource.com> <871x2tnwz0.fsf@us.ibm.com> <20051010170724.GC20935@uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ewan Mellor Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org EM> Sure, and that works now with my fix. Great. I was really just responding to the question about who might run xm as non-root :) EM> I would have applied your patch, but what you'd effectively done EM> was moved the import of XendLogging so that it didn't occur when EM> doing xm help. There was mention a while back about not importing a whole pile of things to simply run a help command or the like, unless it was necessary. I agree with Jeremy that logging inside xm seems a little strange, especially to the same place as the daemon. It makes more sense to me to expect debug information from an interactive tool on the console, and to see info from a daemon in a log file. Maybe a command-line or config-file switch to turn on debug output to stderr? -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com