Reprofile when /lib/modules is updated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sreadahead (Ubuntu) |
Invalid
|
Wishlist
|
Unassigned | ||
ureadahead (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: sreadahead
The /etc/cron.
However, if you imagine there is a kernel update just after the monthly regeneration, then the system boot process will not reach its maximum speed before one month.
I attached a cron script which provide the below features:
- trigger regeneration if there is a major library update (like /lib/module/
- trigger regeneration after 1 month if no major update occured
- prevents to trigger regeneration more than once a week
This script could be placed in the /etc/cron.daily/ directory and could replace the current /etc/cron.
ProblemType: Bug
Architecture: amd64
Date: Fri Oct 9 16:59:48 2009
DistroRelease: Ubuntu 9.10
Package: sreadahead 1.0-4
ProcEnviron:
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: sreadahead
Uname: Linux 2.6.31-12-generic x86_64
XsessionErrors:
(gnome-
(gnome-
(polkit-
(nautilus:1217): Eel-CRITICAL **: eel_preferences
Changed in ureadahead (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
summary: |
- Should profile more often when updates are applied + Reprofile when /lib/modules is updated |
sreadahead includes a dpkg trigger which will cause profiling to be repeated if files in /etc/init or /etc/init.d are changed. This could be trivially extended to include /lib/modules as well, if that is an important bit of readahead data, by adding it to debian/ sreadahead. triggers in the source package.