On Sunday 26 January 2003 13:17, Pixel wrote: > Emmanuel Blindauer <[EMAIL PROTECTED]> writes: > > Le Dimanche 26 Janvier 2003 14:50, Danny Tholen a �crit : > > > Silly enough, fam requires portmap, and fam is used by KDE (and > > > nautilus too i think) to monitor file-changes. It can also poll the > > > disks if fam is not running, but this is worse for performance. > > > > > > drakxservices should (IMO) auto-enable portmap is fam is enabled. > > > (and autodisable fam if there is no portmap) > > > Danny > > > > Why should fam be dependant on portmap ? portmap is mostly used for > > network services, not for monitoring disk. > > Having an open port on a computer, only for one daemon who watch files > > changes is not very good. > > well, i don't think drakxservices et the right place to add services > dependency. Maybe doing it directly in chkconfig would be better. I > don't remember if there's any plan on adding such a feature... > > fredl should know better, than i.
This dependency should at least be visible from drakxservices when the user clicks on the Info button. Think about it: If I hadn't read this email, and I had enabled fam and disabled portmap [in drakxservices] and then rebooted, I would have been up for quite a surprise if I had then seen portmap as a running service ... Regardless of whether you add this dependency into chkconfig, drakxservices or if you decide to ignore it: The user should be able to read about it by clicking the info button for both portmap and fam in drakxservices so that he/she has at least a chance of making a semi-informed decision about whether to enable/disable fam and portmap. This is of course the simplest solution: Overhaul the info text in drakxservices and drop the depencency checking! Narfi.
