lifetime should be configurable

Bug #657033 reported by Scott Moser on 2010-10-08
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Dustin Kirkland 

Bug Description

Lifetime of the instance should be configurable.

In one (and only) one sense, it is.
LIFETIME = 60 * 55;

But we have other places in the code which are forcing 55 minutes.

a.) the countdown timer
b.) the at jobs scheduled

Probably some text in lots of other places.

Dave Walker (davewalker) wrote :

@Scott, I should probably just look myself... but is it using LIFETIME, or literally hardcoded to 55m?

Changed in awstrial:
status: New → Confirmed
importance: Undecided → Medium
Dave Walker (davewalker) wrote :

On another note; it would be "nice" to be able to have a normal setting - as an escalated group, depending on django group memberships.

Changed in awstrial:
status: Confirmed → Triaged
assignee: nobody → Dustin Kirkland (kirkland)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers