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

[Xen-devel] policies on coredump


  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Kip Macy <kip.macy@xxxxxxxxx>
  • Date: Wed, 27 Apr 2005 16:22:05 -0700
  • Delivery-date: Wed, 27 Apr 2005 23:21:52 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=FdQZhPtGZXZIP5kfQkeW6keOW/Fz5iJRKddJpgs8MNK7DqNaCQowy9H0rA3A8klrjA7JTCT8ObWIcJLrouMd4mvS+h4jPjAUgoHrnWcRfQInTndaF/DDOB/LupNevOjczMmsik7XPQ7j/jkH0wovWe54bg0lA5wJo+DZ3e5Wgts=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I'm soliciting opinions on where domU coredumps should be put, if they
should be enabled by default, and what the default naming convention
should be. This will probably all have to change when capabilities are
added, but in the meantime I'd like to know before I submit a patch.


 -Kip

_______________________________________________
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®.