On Tue, Feb 19, 2013 at 4:28 PM, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote: > Without commenting on the general case, I think that in the specific case > the explanation applies. If one wants to add a new directory to the tmpwatch > list, thus modifying the file, and then we (oh for example) change the > location of /usr/sbin/tmpwatch, on update either the new directory will be > lost or else the whole thing will break (depending on whether the file is > noreplace). If one wants to run tmpwatch on a different directory, it is easiest to set up a separate cron entry (either in /etc/cron.daily, or in users' crontab); this avoids the issue. > That said, I believe the plan is to eventually get rid of the systemwide > tmpwatch -- see the comments on this bug: > https://bugzilla.redhat.com/show_bug.cgi?id=866693 Yet nobody bothered to tell the tmpwatch maintainer about "the plan"... Anyway, the /etc/cron.daily/tmpwatch executable-config-file is gone in rawhide, based on a different bug report. Mirek -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
