Date: Mon, 20 Mar 2006 20:12:19 -0800 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Ganbold <ganbold@micom.mng.net> Cc: freebsd-current@freebsd.org Subject: Re: rcorder problem when booting CURRENT Message-ID: <20060321041219.GA31213@flame.pc> In-Reply-To: <441F7991.8000505@micom.mng.net> <441F7635.4090300@micom.mng.net> References: <441F7635.4090300@micom.mng.net> <441F7991.8000505@micom.mng.net> <441F7635.4090300@micom.mng.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2006-03-21 11:42, Ganbold <ganbold@micom.mng.net> wrote: > Hi, > > I have just upgraded my machine from FreeBSD-6.1-PRERELEASE to > FreeBSD-7.0-CURRENT. > > gw# uname -an > FreeBSD gw.micom.mng.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Tue Mar 21 > 09:00:50 ULAT 2006 tsgan@gw.micom.mng.net:/usr/obj/usr/src/sys/GW i386 > > When I restarted the machine right after mergemaster, it said following > error and > didn't run rc scripts. I had to manually start some scripts. > > ... > pid 104(rcorder), uid0: exited on signal 11 (core dumped) > Segmentation fault (core dumped) > ... > [snip stack trace without symbols] On 2006-03-21 11:57, Ganbold <ganbold@micom.mng.net> wrote: > Sorry for the noise. I read UPDATING and found out that > dansguardian startup script was causing the problem. Still a core dump is a core dump. Can you build a debugging version of rcorder and try again? This time the stack trace may be more useful. - Giorgos
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060321041219.GA31213>