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

List:       kde-devel
Subject:    Re: FAM and 3.1rc3
From:       Manuel Amador <amadorm () usm ! edu ! ec>
Date:       2002-11-29 16:44:25
[Download RAW message or body]

El jue, 28-11-2002 a las 18:06, Michael Kreitzer escribió:
> 'cause it all starts when I click on the shortcuts on my desktop that are 
> URL's for either sftp connections or smb connections.  That's when the fam 
> binary itself starts using 100% CPU... I don't kno wmuch about kde's 
> architecture so I'm sure it could be something else... I'm just fishing for 
> answers.
and it enters a strange tight loop.  All applications which are
subscribed to the fam instance experiment odd behavior meanwhile.  I
disabled fam for that reason.

But what bothers me is that, if I do dd if=/dev/zero of=file, and I have
a konqueror window open, fam provokes a situation in konqueror, where
konqueror updates a zillion times.  FAM should send update events to
konqueror at a reasonable pace (half a second maybe?)!  Or maybe the
subscribing application should be able to tell it how often it needs to
know about updates (And the default should still be half a second).

And FAM also causes unmountable removable devices.   Even when I've
closed all Nautilus/Konqueror windows, I can't eject/unmount media
because FAM insists on keeping track of files in it to see if they've
changed.  Absurd! FAM should let go when an unmount is triggered by the
user/system.  On Mandrake, which has supermount, FAM causes horrible
CD-ROM errors (you eject the CD, CD is gulped again, if you manage to
snatch it before the drive closes, you still have /mnt/cdrom listing
files from the CD-ROM which isn't even there anymore).

luck,


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]