Skip site navigation (1)Skip section navigation (2)
Date:      03 Jan 2002 12:26:44 -0500
From:      Joe Clarke <marcus@marcuscom.com>
To:        Geraud CONTINSOUZAS <geraud.continsouzas@dipp.net>
Cc:        gnome@FreeBSD.ORG, ports@FreeBSD.ORG
Subject:   Re: FreeBSD Port: nautilus-1.0.6
Message-ID:  <1010078805.86152.0.camel@shumai.marcuscom.com>
In-Reply-To: <20020103122031.35498fd2.geraud.continsouzas@dipp.net>
References:  <20020103122031.35498fd2.geraud.continsouzas@dipp.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2002-01-03 at 06:20, Geraud CONTINSOUZAS wrote:
> Dear Mr. gnome,
> 
> First of all, I would like to wish you a happy new year. Ok, now, let's talk about business. I'm new in the FreeBSD world, so I don't really know if sending a mail about an issue in installing-using a port is the right thing to do. Pliz let me know if this is a mistake.
> 
> Anyway, to make a long story short : I've kicked Windows out of my box, installed a minimal FreeBSD 4.4, updated the port tree, installed (in this order) XFree86-4.1.0_10, enlightenment-0.16.5_5 and the x11/gnome-1.4.1b2_1 "meta-port". For the most of it, I don't complain : everything's fine. The only annoying thing is that nautilus never started. When I try to launch it, here's what I get (ps waux) : 
> 
> <-- snip -->
> geraud 23540  8.9  3.5 17584 9144  ??  Ss   11:49AM   0:03.12 nautilus
> geraud 24169  7.4  2.9 16088 7368  ??  S    11:50AM   0:00.26 nautilus-throbber --oaf-activate-iid=OAFIID:nautilus_throbber_factory --oaf-ior-fd=12
> geraud 24215  2.0  0.6  1908 1544  ??  R    11:50AM   0:00.02 /usr/X11R6/bin/gconfd-1 18
> 
> And then, a window pops up telling me the gconf daemon can't be reached, and further errors will come on the console
> 
> Eel-WARNING **: GConf error:
>   Failed to create pipe for communicating with spawned gconf daemon: Too many open files in system

Try doing:

sysctl -w kern.maxfiles=5000

and see if that works.  I can't remember if that variable was always
read-write.  It is in a recent -stable.  

kern.maxfiles is actually dependent on your maxusers setting in the
kernel, though.  You have maxusers set too low in your kernel conf.  If
this is 4.4-RELEASE, edit your kernel config, and change maxusers to 64,
then recompile.  If this is a very recent version of 4.4-stable or
4.5-PRERELEASE, set maxusers to 0, then recompile.  More on kernel
limits can be found at:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-kernel-limits.html

Instructions for building a custom kernel can be found at:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html

Joe

> 
> And, now I'm lost. So do you have any idea about what I could do? Do I need to send you more infos? As I told you, I'm pretty new in this wonderful Unix world, and I'm not really sure that the next command line I'll type won't crash my system. But if I can do anything to help, I'm here. Oh, and on the other hand, if I'm THAT dumb that I made a huge and obvious config error or that I made something wrong fell free to yell at me too. :)
> 
> I just hope, I didn't bother you too much with my mail. And once again : Happy New Year
> 
> 
> Sincerely yours,
> Geraud CONTINSOUZAS
> gej@dipp.net
> 
> PS : Oh, I forgot, please apologize my awful, low-leveled english. Thanks a lot. :)
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-gnome" in the body of the message
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-gnome" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1010078805.86152.0.camel>