| 
    
 [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH] Log qemu-dm's message with date, time and pid
 Kevin Wolf writes ("Re: [Xen-devel] [PATCH] Log qemu-dm's message with date, 
time and pid"):
> Or maybe as another option, introduce proper logging functions instead
> of fprintf on stderr into (upstream) qemu. This would be the most work,
> of course, but IMHO also the cleanest solution.
Quite so.
> > I think that my implementation is more safety way because of the
> > following reason.
> > 
> >   qemu-dm can easily restart ioemu-logger when ioemu-logger die.
> >   And ioemu-logger death doesn't affected to guest software.
> 
> ioemu-logger is so simple that it would be a shame to see it crash anyway.
I don't think there is any significant risk of xend dying because it
can't write one of these logs.  xend does lots of logging already of
course.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 
 
  | 
  
![]()  | 
            
         Lists.xenproject.org is hosted with RackSpace, monitoring our  |