From owner-freebsd-gnome@FreeBSD.ORG  Thu Jul 27 23:28:30 2006
Return-Path: <owner-freebsd-gnome@FreeBSD.ORG>
X-Original-To: gnome@freebsd.org
Delivered-To: freebsd-gnome@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8C95E16A4DA
	for <gnome@freebsd.org>; Thu, 27 Jul 2006 23:28:30 +0000 (UTC)
	(envelope-from mvh@ix.netcom.com)
Received: from elasmtp-kukur.atl.sa.earthlink.net
	(elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1305A43D49
	for <gnome@freebsd.org>; Thu, 27 Jul 2006 23:28:30 +0000 (GMT)
	(envelope-from mvh@ix.netcom.com)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com;
	b=JkNxJh5jU/K0a10VZgmJiIaMrQIa2ZicVgN12jRGPFvliNTutQI+fdjrdZHyGpPx;
	h=X-Virus-Scanned:From:To:Subject:Message-Id:Date:X-ELNK-Trace:X-Originating-IP;
Received: from [71.116.145.122] (helo=bsd.mvh)
	by elasmtp-kukur.atl.sa.earthlink.net with asmtp (Exim 4.34)
	id 1G6FHH-0002z5-3c
	for gnome@freebsd.org; Thu, 27 Jul 2006 19:28:27 -0400
Received: from localhost (localhost [127.0.0.1])
	by bsd.mvh (Postfix) with ESMTP id 4C08D17041
	for <gnome@freebsd.org>; Thu, 27 Jul 2006 16:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at bsd.mvh
Received: from bsd.mvh ([127.0.0.1])
	by localhost (bsd.mvh [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Uo94usKNE6CT for <gnome@freebsd.org>;
	Thu, 27 Jul 2006 16:28:21 -0700 (PDT)
Received: by bsd.mvh (Postfix, from userid 1001)
	id 0E15D170A5; Thu, 27 Jul 2006 16:28:17 -0700 (PDT)
From: Mike Harding <mvh@ix.netcom.com>
To: gnome@freebsd.org
Message-Id: <20060727232818.0E15D170A5@bsd.mvh>
Date: Thu, 27 Jul 2006 16:28:17 -0700 (PDT)
X-ELNK-Trace: 2159e7a04884740af66dc3a06d5924d86a56aa8f71a6a4fc046c13f2f5861b47d81f49743ecfecf5350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 71.116.145.122
Cc: 
Subject: gconfd crashes...
X-BeenThere: freebsd-gnome@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: GNOME for FreeBSD -- porting and maintaining
	<freebsd-gnome.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-gnome>,
	<mailto:freebsd-gnome-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-gnome>
List-Post: <mailto:freebsd-gnome@freebsd.org>
List-Help: <mailto:freebsd-gnome-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-gnome>,
	<mailto:freebsd-gnome-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2006 23:28:30 -0000


I have had gconfd-2 crashing lately, which freezes up evolution.  Blah.

Anyway - has this happened to anyone else?

Also, could this be caused by having a tinderbox building away on my
desktop machine (Marcus)?

I did see this in /var/log/messages...

Jul 27 14:59:04 bsd kernel: pid 55827 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:18:52 bsd gconfd (mvh-25589): gmem.c:172: failed to allocate 134217728 bytes
Jul 27 15:18:52 bsd kernel: pid 25589 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:44:20 bsd gconfd (mvh-5149): gmem.c:172: failed to allocate 134217728 bytes
Jul 27 15:44:20 bsd kernel: pid 5149 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:44:22 bsd gconfd (mvh-77369): Failed to get lock for daemon, exiting: Failed to lock '/var/tmp/gconfd-mvh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)
Jul 27 15:46:56 bsd gconfd (mvh-77367): gmem.c:172: failed to allocate 8388608 bytes
Jul 27 15:46:56 bsd kernel: pid 77367 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:47:50 bsd <Jul 27 15:47:50gconfd (mvh-80875): gmem.c:135: failed to allocate 670 bytes
Jul 27 15:47:50 bsd kernel: pid 80875 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:48:17 bsd <Jul 27 15:48:17gconfd (mvh-81150): gmem.c:135: failed to allocate 670 bytes
Jul 27 15:48:17 bsd kernel: pid 81150 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:48:58 bsd <Jul 27 15:48:58gconfd (mvh-81425): gmem.c:135: failed to allocate 670 bytes
Jul 27 15:48:59 bsd kernel: pid 81425 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:49:41 bsd <Jul 27 15:49:41gconfd (mvh-81567): gmem.c:135: failed to allocate 670 bytes
Jul 27 15:49:41 bsd kernel: pid 81567 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:52:16 bsd <Jul 27 15:52:16gconfd (mvh-82195): gmem.c:135: failed to allocate 670 bytes
Jul 27 15:52:16 bsd kernel: pid 82195 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:52:18 bsd gconfd (mvh-84451): Failed to get lock for daemon, exiting: Failed to lock '/var/tmp/gconfd-mvh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)
Jul 27 16:07:22 bsd kernel: pid 84452 (gconfd-2), uid 1001: exited on signal 6
Jul 27 16:07:22 bsd gconfd (mvh-84452): Received signal 11, dumping core. Please report a GConf bug.
Jul 27 16:16:46 bsd kernel: pid 46225 (gconfd-2), uid 1001: exited o
Jul 27 16:16:46 bsd kernel: n signal 6
Jul 27 16:16:46 bsd gconfd (mvh-46225): Received signal 11, dumping core. Please report a GConf bug.

- Mike H.