From josemi@freebsd.jazztel.es  Tue Nov 16 16:42:50 2004
Return-Path: <josemi@freebsd.jazztel.es>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3A0BD16A4CE
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 16 Nov 2004 16:42:50 +0000 (GMT)
Received: from smtp1.jazztel.es (smtp1.jazztel.es [62.14.3.161])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6A59F43D45
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 16 Nov 2004 16:42:49 +0000 (GMT)
	(envelope-from josemi@freebsd.jazztel.es)
Received: from antivirus
	by smtp1.jazztel.es
	with antivirus id 1CU6Q5-0002KY-00
	for FreeBSD-gnats-submit@freebsd.org
	Tue, 16 Nov 2004 17:43:05 +0100
Received: from [212.106.252.3] (helo=rguez.homeunix.net)
	by smtp1.jazztel.es
	with esmtp id 1CU6Q5-0002KN-00
	for FreeBSD-gnats-submit@freebsd.org
	Tue, 16 Nov 2004 17:43:05 +0100
Received: from redesjm.local (orion.redesjm.local [192.168.254.16])
	by rguez.homeunix.net (8.13.1/8.13.1) with ESMTP id iAGGglFK053644
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 16 Nov 2004 17:42:47 +0100 (CET)
	(envelope-from freebsd@redesjm.local)
Received: (from freebsd@localhost)
	by redesjm.local (8.13.1/8.13.1/Submit) id iAGGgliv012937;
	Tue, 16 Nov 2004 17:42:47 +0100 (CET)
	(envelope-from freebsd)
Message-Id: <200411161642.iAGGgliv012937@redesjm.local>
Date: Tue, 16 Nov 2004 17:42:47 +0100 (CET)
From: Jose M Rodriguez <josemi@freebsd.jazztel.es>
Reply-To: Jose M Rodriguez <josemi@freebsd.jazztel.es>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: [PATCH] add fam support to inetd.conf
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         74004
>Category:       conf
>Synopsis:       [inetd.conf] [patch] add fam support to inetd.conf
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Tue Nov 16 16:50:30 GMT 2004
>Closed-Date:    
>Last-Modified:  Sun May 04 04:25:08 UTC 2014
>Originator:     Jose M Rodriguez
>Release:        FreeBSD 5.3-STABLE i386
>Organization:
Redes JM
>Environment:
System: FreeBSD orion.redesjm.local 5.3-STABLE FreeBSD 5.3-STABLE #0: Tue Nov 16 13:26:33 CET 2004 root@orion.redesjm.local:/usr/obj/usr/src/sys/ORION i386


>Description:
	Add a commented out fam line to inetd.conf, to easy fam setup
>How-To-Repeat:
>Fix:

--- patch-inetd.conf begins here ---
--- etc/inetd.conf.orig	Thu Jun 17 22:44:42 2004
+++ etc/inetd.conf	Thu Jun 17 22:48:57 2004
@@ -119,3 +119,7 @@
 #netbios-ssn stream tcp	nowait		root	/usr/local/sbin/smbd	smbd
 #netbios-ns dgram udp	wait		root	/usr/local/sbin/nmbd	nmbd
 #swat	stream	tcp	nowait/400	root	/usr/local/sbin/swat	swat
+#
+# Enable the following entry for fam service
+# This requires a portmapper running, add rpcbind_enable="YES" to /etc/rc.conf
+#sgi_fam/1-2	stream	rpc/tcp	wait	root	/usr/local/bin/fam	fam
--- patch-inetd.conf ends here ---



>Release-Note:
>Audit-Trail:

From: =?UTF-8?B?QmrDtnJuIEvDtm5pZw==?= <bjoern.koenig@alpha-tierchen.de>
To: <freebsd-gnats-submit@FreeBSD.org>, <josemi@freebsd.jazztel.es>
Cc:  
Subject: Re: conf/74004: [PATCH] add fam support to inetd.conf
Date: Sun, 20 Feb 2005 15:02:25 +0100

 Isn't it easy enough to copy and paste the line offered by devel/fam =
 after installation? Besides this line in inetd.conf all alone is not =
 enough to set up fam after installation; therefore it would be an =
 incomplete default.
 
 Regards Bj=C3=B6rn
 

From: Jose M Rodriguez <josemi@freebsd.jazztel.es>
To: =?utf-8?q?Bj=C3=B6rn_K=C3=B6nig?= <bjoern.koenig@alpha-tierchen.de>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: conf/74004: [PATCH] add fam support to inetd.conf
Date: Sun, 20 Feb 2005 20:27:47 +0100

 El Domingo, 20 de Febrero de 2005 15:02, Bj=C3=B6rn K=C3=B6nig escribi=C3=
 =B3:
 > Isn't it easy enough to copy and paste the line offered by devel/fam
 > after installation? Besides this line in inetd.conf all alone is not
 > enough to set up fam after installation; therefore it would be an
 > incomplete default.
 >
 > Regards Bj=C3=B6rn
 
 with this logic, why we distribute an /etc/inetd.conf? all the entries=20
 are commented out.
 
 This is not more or less that the qmail or samba lines.
 
 And is less error prone uncomment a line that copy and paste while=20
 preserve tabs.
 
 =2D-
   josemi

From: =?utf-8?B?QmrDtnJuIEvDtm5pZw==?= <bjoern.koenig@alpha-tierchen.de>
To: "'Jose M Rodriguez'" <josemi@freebsd.jazztel.es>
Cc: <freebsd-gnats-submit@freebsd.org>
Subject: RE: conf/74004: [PATCH] add fam support to inetd.conf
Date: Sun, 20 Feb 2005 22:28:27 +0100

 Jose M Rodriguez wrote:
 
 > with this logic, why we distribute an /etc/inetd.conf? all=20
 > the entries are commented out.
 
 It wasn't logic; just an opinion. It's contestable. You didn't provide =
 logic either, because you claimed that fam is widely used, therefore =
 let's add an default line to inetd.conf. I suppose this is much more =
 true as long as we refer to libfam, but this use doesn't require inetd. =
 Whatever. I think that adding an appropriate line to inetd.conf won't =
 hurt as much as don't do it, but I agree with you that fam is a good =
 candidate for being added to inetd.conf at this time.
 
 > And is less error prone uncomment a line that copy and paste=20
 > while preserve tabs.
 
 It doesn't matter, because spaces are are valid seperators too.
 
 Regards Bj=C3=B6rn
 

From: Jose M Rodriguez <josemi@freebsd.jazztel.es>
To: =?utf-8?q?Bj=C3=B6rn_K=C3=B6nig?= <bjoern.koenig@alpha-tierchen.de>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: conf/74004: [PATCH] add fam support to inetd.conf
Date: Sun, 20 Feb 2005 23:04:54 +0100

 El Domingo, 20 de Febrero de 2005 22:28, Bj=C3=B6rn K=C3=B6nig escribi=C3=
 =B3:
 > Jose M Rodriguez wrote:
 > > with this logic, why we distribute an /etc/inetd.conf? all
 > > the entries are commented out.
 >
 > It wasn't logic; just an opinion. It's contestable. You didn't
 > provide logic either, because you claimed that fam is widely used,
 > therefore let's add an default line to inetd.conf. I suppose this is
 > much more true as long as we refer to libfam, but this use doesn't
 > require inetd. Whatever. I think that adding an appropriate line to
 
 Both gnome and kde uses libfam, but you must have famd running to get=20
 this working.  And the documented method to run famd is from inetd.
 
 You may easy check that, allthought gnome links with libfam, you really=20
 need famd running to get live menu updates.
 
 > inetd.conf won't hurt as much as don't do it, but I agree with you
 > that fam is a good candidate for being added to inetd.conf at this
 > time.
 >
 > > And is less error prone uncomment a line that copy and paste
 > > while preserve tabs.
 >
 > It doesn't matter, because spaces are are valid seperators too.
 >
 > Regards Bj=C3=B6rn
 
 =2D-
   josemi

From: =?utf-8?B?QmrDtnJuIEvDtm5pZw==?= <bjoern.koenig@alpha-tierchen.de>
To: "'Jose M Rodriguez'" <josemi@freebsd.jazztel.es>
Cc: <freebsd-gnats-submit@freebsd.org>
Subject: RE: conf/74004: [PATCH] add fam support to inetd.conf
Date: Mon, 21 Feb 2005 00:27:33 +0100

 Jose M Rodriguez wrote
 
 > Both gnome and kde uses libfam, but you must have famd=20
 > running to get this working.  And the documented method to=20
 > run famd is from inetd.
 >=20
 > You may easy check that, allthought gnome links with libfam,=20
 > you really need famd running to get live menu updates.
 
 I believe you in this point, because I neither know Gnome nor KDE to =
 judge about this. At least just linking against libfam is not an =
 indicator for the necessity to run a FAM daemon. I wrote programs myself =
 which uses libfam and they work well.
 
 Regards Bj=C3=B6rn
 
>Unformatted:
