Date: Sat, 3 Nov 2012 23:27:42 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: Garrett Cooper <yanegomi@gmail.com> Cc: Xin LI <delphij@delphij.net>, current@freebsd.org Subject: Re: watchdogd coredump Message-ID: <20121103232742.000046a3@unknown> In-Reply-To: <CAGH67wTbu9=dKfNkyS9-Yvwg-t02yyYxWY4YR5Bs%2BMtHYo1yJg@mail.gmail.com> References: <20121103225542.00001118@unknown> <CAGH67wTbu9=dKfNkyS9-Yvwg-t02yyYxWY4YR5Bs%2BMtHYo1yJg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 3 Nov 2012 15:13:59 -0700 Garrett Cooper <yanegomi@gmail.com> wrote: > On Sat, Nov 3, 2012 at 2:55 PM, Alexander Leidinger > <Alexander@leidinger.net > > wrote: > > > Hi, > > > > I updated from r239708 to r242511 and my watchdogd coredumps (and > > brings down the system... well, the WD works). > > > > Before I have a deeper look (recompiling with debugging and such) at > > this, can someone confirm that with a recent -current and a WD > > configured to call a shell script which does a simple ls > > to /dev/null there is a segfault in watchdogd? > > > > watchdogd_flags="-e /root/bin/wd_check.sh -s 5 -t 60" > > > > ---snip--- > > # cat /root/bin/wd_check.sh > > #!/bin/sh > > > > exec ls / /space/jails >/dev/null 2>&1 </dev/null > > ---snip--- > Do you have watchdogd_flags set to something non-standard? Xin CCed > since he made the last commit. Please see above. Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121103232742.000046a3>