[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Re: [Xen-changelog] Rewritten XendLogging to not be asingleton class, and not have methods used


  • To: "Dan Smith" <danms@xxxxxxxxxx>, "Ewan Mellor" <ewan@xxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Wed, 12 Oct 2005 22:37:59 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 12 Oct 2005 21:35:46 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcXNv1wL8aPI4nK/Q92YGTv/t6IRxwAHBRnA
  • Thread-topic: [Xen-devel] Re: [Xen-changelog] Rewritten XendLogging to not be asingleton class, and not have methods used

> 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?

Yep, I was slightly surprised to find that xm logged to
/var/log/xend.log

Is it actually useful to have the xm debug output interleaved with the
xend output? If not, I don't think xm should write to xend.log at all.

Ian

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.