[Sheepdog] [PATCH] Enable sheepdog generate core dump file

Yunkai Zhang yunkai.me at gmail.com
Tue Mar 6 16:53:05 CET 2012

On Tue, Mar 6, 2012 at 9:19 PM, Liu Yuan <namei.unix at gmail.com> wrote:
> On 03/06/2012 08:50 PM, Yunkai Zhang wrote:
> >
> >     Here in logger, SIGSEGV usually generated by the exiting of parent
> >     process (caused by prctl).
> >     So it has nothing to do with the core dump of sheep itself.
> >
> >
> > You are right, I haven't noticed that the core dump file would be placed
> > in / directory.
> >
> > Generally, we should put the core dump file in a particular directory so
> > that users can find it easily, maybe  LOCALSTATEDIR+"/lib/sheepdog" will
> > be a good path for it.
> I think neither '/' nor /lib/sheepdog is intuitive enough for an
> ordinary user to locate it, who sometimes care it for debugging
> infrequently.

Not the "/lib/sheepdog" but the "LOCALSTATEDIR/lib/sheepdog" -- the
usually value is "/val/lib/sheepdog",

We can use ./configure --localstatedir="xxx" to change the default

I learn this usage from Corosync source code.

When the program exit abnormally, the core dump file is the most
valuable clues for us.

We should store core dump file carefully, not just for debugging when
we develop it, but also for stable version of sheepdog after we
deployed it in our product environment.
> So where is this core dump file, by a convention, supposed to be located?

> Thanks,
> Yuan

Yunkai Zhang
Work at Taobao

More information about the sheepdog mailing list