I'd think twice about turning sgi-fam off. Obviously the kernel is one who knows about all file changes on the disk. It makes these changes kown to other program through its "dnotify" function. sgi-fam just happens to be the only library that I know of that hooks into dnotify.
When a program subscribes (registers for a callback) to monitor a certain file or directory, it signals an event in your app. Typically the event would be to refresh what your looking at. For example, browse to /var/spool/mail and watch all the inboxs change in real time - without you having to click refresh. Many unix apps go polling bananas. That's a bad performance hit. Imagine all your panel applets having to poll the filesystem every second to update it-self. (ahem... the wire-less monitor applet). If no changes are going on, then why is your applet still asking the same question over and over again and using up CPU time? FAM-enabling them would make them effecient and much more responsive to the user. With enough griping to the programmers, more and more apps are (as they should) becoming fam compliant. -eric wood Bret Hughes wrote: > On Thu, 2003-08-07 at 21:19, Gordon Messmer wrote: >> Bret Hughes wrote: >> It's much more efficient to use FAM, which can simply "ping" the >> application to let it know there's an update, rather than checking >> for updates repeatedly. >> > Makes sense, Thanks. Since I do not use nautilus ( the only thing > whatrequires lists on my 7.3 boxes) I guess I'll leave it off :) > > Bret -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
