On Mon, Jul 23, 2012 at 04:48:19PM -0700, joe shmoe wrote: > Hi, > Thank you for the reply.
You are welcome. > I ended up opting for writing to filesystem rather than > raw_device and this seems to have helped me sidestep the > problem for now. Good move. > Unfortunately, I can't quite make a jump to later sources. > > I do have another question, I see KDUMP_KEEP_OLD_DUMPS mentioned > to automatically clean up prior dumps (for ex: > http://dedoimedo.com/computers/kdump.html > and other SUSE docs). > However, I cannot find any logic in sources to do this (and sure > enough I don't see older cores in my /var/crash/ path clean up > as new cores are dumped). > > Could someone please comment if: > (i) KDUMP_KEEP_OLD_DUMPS is unsupported or not. If it IS supported, > could someone please help with the relevant source code so I could > debug why it isn't working? Yes, I did download kexec-tools git but > cannot find anything relevant. > > (ii) If there is NO explicit source code to achieve this -- then > do folks achieve such a cleanup through KDUMP_PRE and KDUMP_POST scripts? > If yes, is there a standard-ish script out there to achieve this? Sorry but I could not help because I do not use SUSE. But maybe guys from SUSE could point out something. Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
