SystemCleanUpTool

Differences between revisions 3 and 4
Revision 3 as of 2006-06-08 17:57:23
Size: 3262
Editor: bzq-84-108-227-221
Comment:
Revision 4 as of 2006-06-08 19:28:13
Size: 3368
Editor: bzq-84-108-227-221
Comment:
Deletions are marked like this. Additions are marked like this.
Line 26: Line 26:
 * Suggestiong criteria should also consider tradeoff of data aging time, as well as weight of the folder or file. "Heavier" content should be more under the gun then lighter, and older as well.  * Suggestiong criteria should also consider tradeoff of data aging time, as well as weight of the folder or file. "Heavier" content should be more under the gun then lighter, and older more then newer.

 * "System" folders (e.g. /var /tmp /usr ...) should have different matching rules then homes.

Summary

This specification discusses implemeting a small program tool , that would be autoamtically fired each time the predefined minumum free space on a designated file system is reached, and will suggest to the user several ways to free more space in order to be able to resume his work. This is especially useful in system partitions, where not enough free space can make the system in-operable.

Rationale

Often, when actively working on a system, disk space is consumed rapidly until a shortage is experienced. While one can have lots of indisposable content that takes up space, this is often caused by all sorts of redundent data, that accumulates and is often neglected until a shortage is encountered and users actively put effort into deleting it. There should be a solution to warn users before hand, and suggest and carry purge operations for several common residual data, that can be safely removed and immidiately help gain more free space to resume work. Residual data can be log files, package constructions left overs, Garbage Bin contents, unused installed programs, /tmp contents etc, unused language packs and data, old kernels etc..

Use cases

  • Brian is using his desktop computer to do some web development. For that he has several DB servers, and an application server installed. Those application produce alot of log file data, especially under heavy development and experimentation, where he sets them to produce maxium verbosity for debugging purposes. After a week of heavy work, his free space on his / fs reaches the low minimum. the free-disk-space wizard detects that, and before Brian is running into operation problems, it offer him to free some old logs that occupie most of the space currently on his / fs. He confirms the removal, and resume working. (the wizard takes care to do the removal in the background). The interaction with Brian is done through the desktop notficiation infrastructure.
  • George has been reciving lots of audio visual content recently, from relatives overseas. He burnt them all to DVDs, and made sure to move to the garbage bin every file he had burnt. After a while of doing so, he does not notice his free space in his home folder dropped to the minimum allowed. He is also downloading a big iso file of the edgy desktop-cd for testing. The disk space freeing tool detects that there is not enough free space, and pops up a desktop notification for Geroge, suggesting that there is large amount of data in .Trash, that can be purged, to make more room. George acknowledges, space is freed and the download is saved.

Scope

Design

  • Suggestiong criteria should also consider tradeoff of data aging time, as well as weight of the folder or file. "Heavier" content should be more under the gun then lighter, and older more then newer.
  • "System" folders (e.g. /var /tmp /usr ...) should have different matching rules then homes.

Implementation

Code

Data preservation and migration

Outstanding issues

BoF agenda and discussion


CategorySpec

SystemCleanUpTool (last edited 2008-08-06 16:16:56 by localhost)