missing locking / changetrack does only track with a delay of one day and one hour
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
changetrack (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
issue: changetrack currently is _not_ integrated into package installation. Effectively,
this means that new config files will be added at worst 25 hours late (cron.daily/
Possibly after the user already changed some config files.
solution: call changetrack with the list of newly added config files as defined
by the packages, and append that list the list of all packages.
a similar situation exists, when the user edits /etc/changetrac
work around:
manually invoke cron.daily/
then cron.hourly/
however this shows a second issue:
issue: changetrack and scripts messing with the filelists require locking to avoid data corruption.
This certainly is the case for the filelist itself. And I'm quite a bit sceptical concerning RCS in
face of multiple concurrent attempts at the same file.
solution: add locking, for now at least to the cronjobs, in the following example using
lockfile from the procmail package:
f=/var/
<original content of cron.*/changetrack>
rc=$?;rm $f;exit $rc
Changetrack would also profit from adding locking internally, but even than, we'd need still
to use locks in the daily script.
thanx,
Peter
Jaunty
changetrack 4.3-3
LSB Version: core-2. 0-amd64: core-2. 0-noarch: core-3. 0-amd64: core-3. 0-noarch: core-3. 1-amd64: core-3. 1-noarch: core-3. 2-amd64: core-3. 2-noarch: core-4. 0-amd64: core-4. 0-noarch