Add a commented out fam line to inetd.conf, to easy fam setup
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
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
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
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
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
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped
It looks to me like fam has been replaced with kqueue in both KDE and GNOME, which appear to be the canonical examples where it was used back in the day. Feel free to re-open this bug if you still think it's relevant, but I'm taking the liberty of closing this as overcome by events.