From owner-freebsd-questions Sat Nov 3 20:41:49 2001 Delivered-To: freebsd-questions@freebsd.org Received: from soda.csua.berkeley.edu (soda.CSUA.Berkeley.EDU [128.32.247.226]) by hub.freebsd.org (Postfix) with ESMTP id D193037B405 for ; Sat, 3 Nov 2001 20:41:45 -0800 (PST) Received: from localhost (mjm@localhost) by soda.csua.berkeley.edu (8.11.6/8.11.4) with ESMTP id fA44fYW68913; Sat, 3 Nov 2001 20:41:39 -0800 (PST) (envelope-from joup@bigfoot.com) X-Authentication-Warning: soda.csua.berkeley.edu: mjm owned process doing -bs Date: Sat, 3 Nov 2001 20:41:34 -0800 (PST) From: Mark Miller X-X-Sender: mjm@soda.csua.berkeley.edu To: FreeBSD user Cc: freebsd-questions@freebsd.org Subject: Re: getting fam to work w/ kde2.2.1 In-Reply-To: <20011103212155.U27717-100000@Amber.XtremeDev.com> Message-ID: <20011103203517.I65525-100000@soda.csua.berkeley.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG *KDED* needs fam (the File Alteration Monitor), I believe (sorry, I should have clarified). If there's no fam, starting kde can take upwards of 5-10 minutes while kded figures out that fam isn't there. Killing kded during this time will cause kde's startup to proceed as normal. But all of that's kind of a side-issue: I've got fam running now, and I'm much happier with startup times (for both kde itself and kde apps). So, 1) is it possible to run fam sans portmap, and 2) what are the security risks of running portmap for this sole purpose? Thanks for your help, Mark On Sat, 3 Nov 2001, FreeBSD user wrote: >KDE needs fam to work? I've disabled it here, haven't ran into anything >that didn't work. What exactly does fam do? > >On Sat, 3 Nov 2001, Mark Miller wrote: > >> Hi, >> >> When I first started w/ freebsd (4.2-RELEASE) I followed the mantra of >> disabling everything that I didn't explicitly need-- inetd, telnetd, >> etc. Among the list was portmap. But now kde uses fam, and fam needs >> portmap. Is it possible to run fam without portmap? What are the >> security risks involved with keeping portmap running? I've got a fairly >> strict /etc/hosts.allow file (only allows ssh connections from certain >> IPs, denies all other requests), is that enough? What else can I do to >> secure portmap? >> >> >> Thanks, >> Mark Miller >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-questions" in the body of the message >> >> >> > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message