Hi! On upgrade to the version I compiled with Thibaut corrupted configuration file detection patch from bug #515653...
merkaba:/etc> LANG=C apt-cache policy uptimed
uptimed:
Installed: 1:0.3.16-3.1~thibaut
Candidate: 1:0.3.16-3.1
Version table:
1:0.3.16-3.1 0
500 http://ftp.de.debian.org/debian/ sid/main amd64 Packages
*** 1:0.3.16-3.1~thibaut 0
100 /var/lib/dpkg/status
... it overwrote the maxrecord setting again:
merkaba:/etc> bzr diff
=== modified file 'uptimed.conf'
--- uptimed.conf 2011-05-21 14:35:17 +0000
+++ uptimed.conf 2011-06-01 10:12:43 +0000
@@ -4,7 +4,7 @@
UPDATE_INTERVAL=600
# Maximum number of entries in logfile. Set to 0 for unlimited.
-LOG_MAXIMUM_ENTRIES=0
+LOG_MAXIMUM_ENTRIES=50
# Minimum uptime that must be reached for it to be considered a record.
LOG_MINIMUM_UPTIMED=1h
I did change it manually to unlimited records cause initial debconf
configuration didn´t ask.
This time no aborted debconf process was involved. It was just a regular
upgrade. And it didn´t ask me whether to apply that change.
Actual results:
uptimed upgrade overwrote the max record setting it didn´t ask for
initially. When the machine had more than 50 records then uptimed would
have truncated the database thus loosing data. So this is a potential data
loss bug!
Expected results:
It either leaves the configuration file alone or asks me whether I would
like this change.
Another solution would be to have it ask the max record setting on initial
configuration, then debconf would have the right value from the beginning.
But then this still would not help when the user later manually adapts the
setting.
I prefer when uptimed would leave uptimed.conf alone at upgrades except
when the configuration file format changes or a new option is added, and
then it should ask like other package upgrades do as well.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
signature.asc
Description: This is a digitally signed message part.
