Bug 85524
| Summary: | konqueror does not cause fam to be started | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Public Beta | Reporter: | Michael Wardle <michael.wardle> |
| Component: | kdebase | Assignee: | Than Ngo <than> |
| Status: | CLOSED NOTABUG | QA Contact: | Ben Levenson <benl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | phoebe | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-03-03 23:10:19 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Fam is disable in KDE by default. It has caused many problem in earlier KDE version. KDirWatch works fine in KDE. |
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): fam-2.6.8-9 portmap-4.0-52 xinetd-2.3.10-4 kdelibs-3.1-7 kdebase-3.1-7 How reproducible: Always 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.