Hello Thibault, Rhanks for your effort. I'll take a look at this script. As an alternative to the reverse engineering I can propose command line tool using Java. Or maybe extend current command line admin (OPENMEETINGS-111) On Apr 6, 2012 5:28 PM, "Thibault Le Meur" <[email protected]> wrote:
> Hi, > > It seems that OM doesn't delete streams form the filesystem. Thus I > needed a way to track diskspace usage of streams so I developped a "not > so quick and yet dirty script" to do the following tasks: > * delete streams marked as deleted in OpenMeetings DB from the filesystem > * report diskspace used by not deleted streams with associated > information (owner, room, ...) > * report diskspace per user, and send an overquota email if needed > * report streams older than and Expiration duration threshold and send > an expriation email if needed > > It requires: > * linux system > * openmeetings with mysql DB (tested on openmeetings_1_9_1_r4707) > * mysql client, a mysqk user able to do selects to the OM DB > * usual linux tools like cut, awk, sed and bash 4.x > > It comes with no warranty as I had to reverse engineer the DB to > understand how streams ar recorded and marked as deleted and I'm quite > sure there are things I missed so It may be considered as a "template". > I just post it here, in case it can prove to be usefull to someone. > > Now I would need help on how uploaded files are recorded to filesystem > and DB to do the same for these ones. If anyone can help me... ;-) > > Regards, > Thibault >
