Bug 84249 - konqueror does not always release fam modification notification
Summary: konqueror does not always release fam modification notification
Status: RESOLVED DUPLICATE of bug 78322
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-30 10:24 UTC by Éric Brunet
Modified: 2004-06-30 10:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Éric Brunet 2004-06-30 10:24:29 UTC
Version:            (using KDE KDE 3.2.3)
Installed from:    RedHat RPMs
Compiler:          i686 Fedora Core 2 + Updates 
OS:                Linux

When you look at a directory with konqueror, the fam
server is asked to monitor that directory and all the
directories within and to report to konqueror when
something changed in those directories.

Normally, when you change directory in your konqueror window or when you close that konqueror window, the list of items fam has to monitor is changed.

However, that does not always happen. Sometimes (quite often, actually, but not always), you can quit a konqueror window and still have fam monitoring the directories you were looking at. I can tell by running lsof and look at
the directories that fam has opened.

It would not usually be a big problem, except when the directories being monitored are /mnt/cdrom, /mnt/zip, /mnt/flash, etc. When that happens, you cannot unmount your removable media because that stupid fam is still holding an openend file descriptor on the mounted directory, and there is nothing that you can do short of killing fam.

In short, two things:
	konqueror should be extra carefull to tell fam to stop monitoring the directories it doesn't need to have monitored anymore
	when the kde unmount procedure fails, it should
check if it didnt happen to fail because of fam, and take
action (I don't know how) or at least explain the user.
Comment 1 Tommi Tervo 2004-06-30 10:32:09 UTC

*** This bug has been marked as a duplicate of 78322 ***