Bug 85524 - konqueror does not cause fam to be started
konqueror does not cause fam to be started
Product: Red Hat Public Beta
Classification: Retired
Component: kdebase (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2003-03-03 17:19 EST by Michael Wardle
Modified: 2007-04-18 12:51 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-03-03 18:10:19 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Wardle 2003-03-03 17:19:42 EST
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): 
How reproducible: 
Steps to Reproduce: 
1. Install Phoebe 3 
2. Start a KDE session 
3. Open Konqueror 
Actual results: 
fam is not shown in the process list 
Expected results: 
fam is shown in the process list 
(it should be started on demand using xinetd) 
Additional info: 
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.
Comment 1 Ngo Than 2003-03-03 18:10:19 EST
Fam is disable in KDE by default. It has caused many problem in earlier KDE
version. KDirWatch works fine in KDE. 

Note You need to log in before you can comment on or make changes to this bug.