Cronify the mailin script
Bug #341152 reported by
Paul Everitt
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KARL3 |
Fix Released
|
Medium
|
Chris Rossi |
Bug Description
Once things are working acceptably, cronify it. Shove the output data in /var/log.
We can't do eval of emailin until this is done, obviously, but this shouldn't be done until some of the showstoppers are closed.
Changed in karl3: | |
assignee: | nobody → chris-archimedeanco |
importance: | Undecided → Medium |
milestone: | none → m5 |
Changed in karl3: | |
status: | New → In Progress |
Changed in karl3: | |
status: | In Progress → Fix Committed |
Changed in karl3: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The mailin script is now a very old man.
Notes:
1) The mailin script is very chatty. Even if there is no mail to process you're getting about 700 bytes in the log every time it's run. That's about a megabyte of noise a day if we're running at one minute intervals.
2) Mailin is not tied into the alert system yet. I'm guessing I'll probably get to implement that one--just want to make sure it doesn't fall off the radar.