[request-tracker-maintainers] Cron jobs

[Dominic Hargreaves]

On Mon, Jan 18, 2010 at 11:48:25AM +0000, Dominic Hargreaves wrote:
> On Thu, Dec 03, 2009 at 09:06:25PM +0200, Niko Tyni wrote:
> > On Tue, Dec 01, 2009 at 09:46:11PM +0000, Dominic Hargreaves wrote:

> > > So, does anyone have any opinions on the following possibilities:
> > > 
> > > 1 add them in a normal config file, and leave for the user to disable
> > >   if they want
> > > 2 add them in a normal config file, commented out, and let the user
> > >   know they need to enable them to get the full functionality
> > > 3 generate the cron job file based on the response to a debconf question
> > >   about whether they should be enabled (has the advantage that we could
> > >   ask about the user to run the cron jobs as - would default to www-data)
> > > 4 something else?
> > 
> > I think it's a bit of borderline case between 1 and 3.
> > 
> > The debconf thing allows for more flexibility - maybe set the default
> > based on whether dbconfig-common is opted in? That way people who don't
> > want anything automagical to happen should be content and the rest would
> > have a working system out of the box.
> > 
> > Medium priority for the enabling question and low priority for the cron job
> > user would seem appropriate to me.
> 
> Given the above about how they behave with unconfigured questions, 3 is
> going to be better, and I like your idea about how to tie in the debconf
> stuff. I'll try and get this done soon.

I've kept it simple for now and only have one question, marked medium
defaulting to on.

In subversion now, waiting for debconf translations before uploading.

Dominic.

-- 
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)