Red Hat Bugzilla – Bug 85524
konqueror does not cause fam to be started
Last modified: 2007-04-18 12:51:49 EDT
Description of problem:
Konqueror can (and should?) use FAM to find out when a file has changed
and immediately refresh the file list. When I log in to a KDE session and
start Konqueror, "ps" does not show FAM as having been started, despite
the portmap, xinetd, and fam services all being enabled. When a file is
changed, Konqueror takes a few seconds to reflect this change.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Phoebe 3
2. Start a KDE session
3. Open Konqueror
fam is not shown in the process list
fam is shown in the process list
(it should be started on demand using xinetd)
This is a mostly default install of Red Hat Linux 8.0.94 (Phoebe 3).
The FAM configuration has not been changed, and FAM works fine
in conjunction with Nautilus.
Fam is disable in KDE by default. It has caused many problem in earlier KDE
version. KDirWatch works fine in KDE.