[Holger Levsen] > Readahead works for me on etch since I upgraded to 2.6.22-4, still > using 1.20060421.1016-1~bpo+40+1 > > I've reported this in > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465273#25
I know, but I have a hard time to believe that readahead-watch is able to store its pid file before /var/run/ is writable, and thus leaving stop-readahead with no pid file to read to figure out the pid to stop at the end of the boot. I assume here that you mean that 'readahead works' as in a profile run with readahead works. In short, I doubt you are testing the problematic thing, as I still was able to reproduce the problem in a qemu test run of lenny. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
