603338 - FlightDeck still leaving large directories in /tmp

Status: RESOLVED FIXED

(Mozilla Labs Graveyard :: FlightDeck, defect, P1)

Description

[Zandr Milewski [:zandr]]

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.

Comment 1

[Daniel Buchner [:dbuc]]

I am bumping this to make sure we add that cron job Wil mentioned before the next release.

Comment 2

[Wil Clouser [:clouserw]]

Our quick fix here is to create a cron job to delete files over a day old

Comment 3

[Andy McKay]

https://github.com/andymckay/FlightDeck/commit/d1f4c0412df0f0a88c8fcaad3fad03b9752e0336

Comment 4

[Andy McKay]

Called by: manage.py cron clean_tmp

Comment 5

[Wil Clouser [:clouserw]]

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

Comment 6

[Andy McKay]

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.

Comment 7

[Wil Clouser [:clouserw]]

ah, yeah.  We won't know until it's deployed (see bug 600013).  I guess we can't do it for now then.

Comment 8

[Andy McKay]

Well added anyway, easy to change once deployed.

Comment 9

[Piotr Zalewa [:zalun]]

one can get a shell's dir as this

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