On Wed, Feb 20, 2013 at 01:31:49PM +0100, Miloslav Trmač wrote:
> 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.
In which case, maybe it shouldn't be marked as a con
On Tue, Feb 19, 2013 at 4:28 PM, Matthew Miller
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 /
On Tue, Feb 19, 2013 at 3:43 PM, Sergio Belkin wrote:
> Hi, rpmlint complains about cron files, is that a bug?
>
> For example:
>
> tmpwatch.x86_64: E: executable-marked-as-config-file
> /etc/cron.daily/tmpwatch
> Executables must not be marked as config files because that may prevent
> upgrades f
Thanks guys
2013/2/19 Miroslav Suchý
> On 02/19/2013 03:43 PM, Sergio Belkin wrote:
>
>> Hi, rpmlint complains about cron files, is that a bug?
>>
>> For example:
>>
>> tmpwatch.x86_64: E: executable-marked-as-config-**file
>> /etc/cron.daily/tmpwatch
>> Executables must not be marked as config
On 02/19/2013 03:43 PM, Sergio Belkin wrote:
Hi, rpmlint complains about cron files, is that a bug?
For example:
tmpwatch.x86_64: E: executable-marked-as-config-file
/etc/cron.daily/tmpwatch
Executables must not be marked as config files because that may prevent
upgrades from working correctly.
On Tue, Feb 19, 2013 at 11:43:53AM -0300, Sergio Belkin wrote:
> Hi, rpmlint complains about cron files, is that a bug?
> For example:
> tmpwatch.x86_64: E: executable-marked-as-config-file
> /etc/cron.daily/tmpwatch
> Executables must not be marked as config files because that may prevent
> upgrad
