Public bug reported:
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/changetrack).
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/changetrack.cfg.
work around:
manually invoke cron.daily/changetrack to update the config file list,
then cron.hourly/changetrack to update RCS.
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/lib/changetrack/.locked; lockfile -s10 -l600 $f
<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
** Affects: changetrack (Ubuntu)
Importance: Undecided
Status: New
** Tags: apt changetrack jaunty race
--
missing locking / changetrack does only track with a delay of one day and one
hour
https://bugs.launchpad.net/bugs/413775
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
