FlightDeck still leaving large directories in /tmp

RESOLVED FIXED in 0.6

Status

P1
blocker
RESOLVED FIXED
8 years ago
8 years ago

People

(Reporter: zandr, Assigned: andy+bugzilla)

Tracking

Trunk
x86
Mac OS X

Details

(Reporter)

Description

8 years ago
FlightDeck filled the disk again this morning. It appears that the directories created in /tmp are still not being cleaned up.

As these are ~7MB each, this chews up disk space in pretty short order.
Assignee: nobody → zaloon
Blocks: 600013
Target Milestone: -- → 1.0
I am bumping this to make sure we add that cron job Wil mentioned before the next release.
Severity: normal → blocker
Priority: -- → P1
Our quick fix here is to create a cron job to delete files over a day old
Assignee: zaloon → amckay
Target Milestone: 1.0 → 0.6
(Assignee)

Comment 3

8 years ago
https://github.com/andymckay/FlightDeck/commit/d1f4c0412df0f0a88c8fcaad3fad03b9752e0336
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
(Assignee)

Comment 4

8 years ago
Called by: manage.py cron clean_tmp
awesome.  Can you add a "crontab" directory to /scripts/ and put this in there?  (see how we do it in zamboni).  This way we can control cron timings and we'll always know what is running in production
(Assignee)

Comment 6

8 years ago
Anyone know what the paths on production are? Or whom to ask? Need to know the full path to FlightDeck and the FlightDeck virtual env.
ah, yeah.  We won't know until it's deployed (see bug 600013).  I guess we can't do it for now then.
(Assignee)

Comment 8

8 years ago
Well added anyway, easy to change once deployed.
one can get a shell's dir as this

abspath=$(cd ${0%/*} && echo $PWD/${0##*/})                                     
echo `dirname $abspath`

Updated

8 years ago
Component: FlightDeck → FlightDeck
Product: Mozilla Labs → Mozilla Labs Graveyard
You need to log in before you can comment on or make changes to this bug.