[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Kicker / famd bug
From:       Waldo Bastian <bastian () kde ! org>
Date:       2002-05-14 22:36:37
[Download RAW message or body]

On Tuesday 14 May 2002 02:16 pm, Gregor Jasny wrote:
> Both the kicker and the famd process took 50% CPU time.
>
> Is this a known bug?
> Should I file a bug report against this?

I guess KDirWatch should stay far away from /dev.

Cheers,
Waldo
-- 
bastian@kde.org  |   SuSE Labs KDE Developer  |  bastian@suse.com

["kdirwatch.patch" (text/x-diff)]

Index: kdirwatch.cpp
===================================================================
RCS file: /home/kde/kdelibs/kio/kio/kdirwatch.cpp,v
retrieving revision 1.73
diff -u -p -r1.73 kdirwatch.cpp
--- kdirwatch.cpp	2002/04/18 05:17:24	1.73
+++ kdirwatch.cpp	2002/05/14 22:34:39
@@ -449,6 +449,8 @@ void KDirWatchPrivate::addEntry(KDirWatc
 				Entry* sub_entry, bool isDir)
 {
   QString path = _path;
+  if (path.startsWith("/dev/") || (path == "/dev"))
+    return; // Don't even go there.
 
   if ( path.length() > 1 && path.right(1) == "/" )
     path.truncate( path.length() - 1 );

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]