dnf installs cron.hourly

Steve Gordon sgordon at redhat.com
Fri Mar 15 16:13:27 UTC 2013


----- Original Message -----
> From: "seth vidal" <skvidal at fedoraproject.org>
> To: "Development discussions related to Fedora" <devel at lists.fedoraproject.org>
> Cc: sgordon at redhat.com
> Sent: Friday, March 15, 2013 12:07:00 PM
> Subject: Re: dnf installs cron.hourly
> 
> On Fri, 15 Mar 2013 11:58:33 -0400 (EDT)
> Steve Gordon <sgordon at redhat.com> wrote:
> 
> > ----- Original Message -----
> > > From: "Daniel P. Berrange" <berrange at redhat.com>
> > > To: "Development discussions related to Fedora"
> > > <devel at lists.fedoraproject.org> Sent: Friday, March 15, 2013
> > > 11:48:41 AM Subject: Re: dnf installs cron.hourly
> > > 
> > > On Fri, Mar 15, 2013 at 10:45:03AM -0500, Jon Ciesla wrote:
> > > > On Fri, Mar 15, 2013 at 10:30 AM, Miloslav Trmač
> > > > <mitr at volny.cz>
> > > > wrote:
> > > > 
> > > > > On Fri, Mar 15, 2013 at 4:11 PM, Daniel P. Berrange
> > > > > <berrange at redhat.com>
> > > > > wrote:
> > > > > > Users shouldn't have to go searching out that kind of thing
> > > > > > in
> > > > > > a
> > > > > > separate package IMHO, it could just be part of stock yum
> > > > > > install.
> > > > > > If it needs to be optional a config param would suffice,
> > > > > > rather than the big hammer of installing/uninstalling extra
> > > > > > RPM to enable/
> > > > > > disable a feature.
> > > > >
> > > > > Yeah, we don't generally do configuration by package
> > > > > installation/uninstallation.
> > > > >
> > > > 
> > > > More to the point,
> > > > https://fedoraproject.org/wiki/Starting_services_by_default
> > > 
> > > That's about starting system services by default though, so isn't
> > > directly relevant to the question of whether cron jobs are
> > > allowed
> > > to be enabled by default. Do we have any package docs about cron
> > > job enablement ?  I couldn't find any in my search attempts.
> > > 
> > > Daniel
> > 
> > The list of files sitting in my /etc/cron.*/ directories would
> > certainly indicate that even if there is such a rule it is being
> > ignored. Not that I necessarily have a problem with that given the
> > jobs that are there (mlocate, cups, logrotate, man-db are all
> > examples I don't remember setting up myself).
> > 
> 
> To be fair - none of those call out to the network.
> 
> they all act on things locally.

Right, but the packaging guidelines don't seem to mention whether you should enable cron jobs in packages by default (or not) at all - let alone provide enough detail to specify what types of jobs it's appropriate for. I'd agree with Jon's comment that there is probably some clarification required in the guidelines here.

Steve


More information about the devel mailing list