Date: Sun, 20 Feb 2005 22:10:14 GMT From: Jose M Rodriguez <josemi@freebsd.jazztel.es> To: freebsd-bugs@FreeBSD.org Subject: Re: conf/74004: [PATCH] add fam support to inetd.conf Message-ID: <200502202210.j1KMAEac002094@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR conf/74004; it has been noted by GNATS. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200502202210.j1KMAEac002094>