Dear Madam or Sir!
I have read your FAQ and can prove the problem of famd getting into a spin
when a huge number of files get alterated.
This version came with Debian 3.1r0a "Sarge" of LOB.de.
I recommend using an exponential back-off scheme when a huge bunch of files
change like deliberately sleeping an increasing number of milliseconds as
long as DNotify events come in faster than a defined threshold. This will
prevent famd from becoming a CPU hog, it's a humble AMD K6II/500 instead of
16 Opterons or so.
Editing out the "-T 0" deep in the startup scripts didn't help because the
DNotify events will keep famd up.
There is also need for a famc, a FAM controller that may inspect and tune
famd. There'll be need of support for the various GUI widget sets.
Aye, there are some security issues, but that will be with any program
accepting user input, either local or remote, you can even wedge malware
between a tty and stdin. It may just need more efforts than under Windows
with its fine granular modularity and excessive integration. Also *NIX had
to cope with hackers almost from Day One, even before the ARPANet came into
existence, phone lines can't be trusted as well.
Kind Regards
Norbert Grün (gnor-gpl@xxxxxx)
--
"Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail
|