Erich Schubert wrote: >Hi, > > >>>Which one? I already wrote a readahead daemon for initng, and converted >>>it into a seperate daemon not long ago. >>> >>> > >google for "google summer-of-code readahead" - first hit is the >proposal. And if you grab the domain name it will lead you to >http://sourceforge.net/projects/preload >(which has the code in CVS) and his blog http://mces.blogspot.com/ > > Hm, just looked at it, it's a lot cleaner than mine (since mine is converted code from something different), he uses a system that monitors /proc, which I tried first but found way too inaccurate for my needs.
I use inotify (needing kernel 2.6.13), the advantage is I will catch every file accessed in directories I monitor, the disadvantage is that it takes some time to setup monitoring those dirs (need one open on all directories, which causes some io wait). >best regards, >Erich Schubert >-- > erich@(mucl.de|debian.org) -- GPG Key ID: 4B3A135C (o_ > To understand recursion you first need to understand recursion. //\ > Wo befreundete Wege zusammenlaufen, da sieht die ganze Welt für V_/_ > eine Stunde wie eine Heimat aus. --- Herrmann Hesse > >_______________________________________________ >initscripts-ng-devel mailing list >[email protected] >http://lists.alioth.debian.org/mailman/listinfo/initscripts-ng-devel > > > _______________________________________________ initscripts-ng-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/initscripts-ng-devel
