Comment 4 for bug 452782

I read the man page and the .conf file in /etc/init and wondered if stopping the profiling earlier would help.

Varied the run time allowed for profiling by changing the "-t 0" in /etc/init/sreadahead.conf and found that for times under 60 seconds it completed and created a /var/lib/sreadahead/pack file.

The size of the pack file for various run times:

-t 10 76208
-t 20 111760
-t 30 159456
-t 40 231440
-t 50 290752
-t 60 pack not created, crashed as described in this bug.

So it looks like when profiling, it doesn't terminate gracefully when the pack file is full, or there's a file on my system between 50 and 60 seconds with a path length > 176, or some other sort of corrupting characteristic, or ?

I contemplated the debug (-d) option, but reading the init documentation and discussion of forking left me wondering just where the sysout would get written. If debug output from a crashing run would help, I'll need help configuring where sysout goes, and/or where to look for it afterwards.