Skip site navigation (1)Skip section navigation (2)
Date:      17 Feb 2003 19:11:29 +0100
From:      Franz Klammer <klammer@webonaut.com>
To:        Joe Marcus Clarke <marcus@marcuscom.com>
Cc:        FreeBSD GNOME Users <gnome@freebsd.org>
Subject:   Re: fam didn't work with nautilus if nautilus-scripts doesn't exists.
Message-ID:  <1045505488.673.7.camel@ds9.webonaut.com>
In-Reply-To: <1045504446.88166.12.camel@shumai.marcuscom.com>
References:  <1045488392.1343.26.camel@ds9.webonaut.com> <1045504446.88166.12.camel@shumai.marcuscom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Am Mo, 2003-02-17 um 18.54 schrieb Joe Marcus Clarke:
> On Mon, 2003-02-17 at 08:26, Franz Klammer wrote:
> > hello!
> > 
> > FYI:
> > 
> > today i've tried to make fam running with my gnome2.2-desktop
> > and for testing i've started fam in the foregrounde and verbose:
> > 
> > fam[5826]: can't chdir("/home/klammer/.gnome2/nautilus-scripts"): No
> > such file or directory
> > 
> > without this directory nautilus recognize no file changes.
> 
> I didn't encounter this problem.
> 
> > 
> > also the portmap resp. rpcbind must startet and i had to start
> > it as daemon and not from inetd.
> 
> Yeah, I did run into this.  fam works from inetd, but this is what you
> need to do:
> 
> * Add rpcbind_enable to rc.conf (portmap_enable on -STABLE)
> * Make sure fam is properly added to inetd.conf, and that inetd is set
> to start in rc.conf (it doesn't by default on -CURRENT)
> * Reboot
> 
> After doing that, fam will work properly from inetd on -CURRENT.
> 

i've done everything except the reboot. only a "killall nautilus".
seems that wasn't enough. nautilus works now with fam from inetd.

thanks! 

franz.


> Joe

-- 


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?1045505488.673.7.camel>