You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (JIRA)" <ji...@apache.org> on 2014/02/05 05:44:12 UTC
[jira] [Closed] (OPENMEETINGS-849) some remains after the purge of
deleted recordings and a system cleanup via admin.sh
[ https://issues.apache.org/jira/browse/OPENMEETINGS-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik closed OPENMEETINGS-849.
-----------------------------------------
Closing resolved issues related to 3.0.0 release
> some remains after the purge of deleted recordings and a system cleanup via admin.sh
> ------------------------------------------------------------------------------------
>
> Key: OPENMEETINGS-849
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-849
> Project: Openmeetings
> Issue Type: Bug
> Components: Audio/Video
> Affects Versions: 2.2.0 Apache Release
> Environment: debian squeeze
> Reporter: Michael Wuttke
> Assignee: Maxim Solodovnik
> Priority: Minor
> Fix For: 3.0.0 Apache Release
>
>
> When I delete the recordings via the OM GUI as the moderator a
> OM room all the captured files will still be in the session folder f.e.:
> /usr/lib/red5/webapps/openmeetings/streams/1
> The cleanup/purge of the deleted recordings works with:
> /usr/lib/red5/admin.sh -v -f --cleanup.
> The whole folder with the captured files will be purged.
> In my case it was the folder ~/streams/1:
> And the recording files in the folder ~/streams/hibernate the files flvRecording_1.flv, flvRecording_1.avi and flvRecording_1.jpg will be deleted.
> But in the folder ~/streams/hibernate the file flvRecording_1.flv.meta
> and in the tables flvrecording, flvrecording_log, flvrecording_metadata and flvrecording_meta_delta of the openmeetings database all the entries for
> the deleted recording still exists.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)