On Tue, Apr 28, 2015 at 4:04 AM, Matteo Sisti Sette <[email protected]> wrote: > On 28/04/15 06:24, Sandro Tosi wrote: >> nope, the cron is a conffile, as you can see with >> >> $ dpkg --status mrtg | grep -A3 Conf >> Conffiles: >> /etc/logrotate.d/mrtg adc9405c8ad58d86ef5de00563c3407b >> /etc/mrtg.cfg 65797ef4da55f538556c6754182fd5b1 >> /etc/cron.d/mrtg 89d528bcb179858f61e8af4363f0c04c >> >> so it will only be removed on --purge > > > Well, then it shouldn't be a conffile. > If you leave a cron installed that executes a binary that no longer exists, > it will produce errors.
if you have looked at the script[1] you would have noticed that is a no-op, once either the binary or the config file are missing. [1] http://sources.debian.net/src/mrtg/2.17.4-2/debian/cron.d/ > One shoudn't explicitly have to do --purge to have an uninstall that does > not result in a system executing dead crons producing errors. this cron doesn't produce any error. > Even if the cron was written in such a way that it does a check and avoids > producing errors (I deleted it so I can't check if it was the case), it's > still wrong to leave a dead cron after uninstallation. It's not a piece of > "configuration", it's something that runs (even if it just runs to do a this is a conffile because users might want to change its behaviour (like the scheduling time) and that must be preserve upon upgrades -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
