Hi Chris, there is no ticket open as this is intended behavior (or a bug by desing :-) The reasoning behind having three separate copies is the following:
1) /workspace is a temporary file and should be removed when running the "cleanup" operation 2) The items in /downloads and /stream cannot be linked against one another because both are individual distribution channels and have (by design) no knowledge about each other. In addition 3) In production environments, you won't usually serve downloads and/or streams from the box that is running your ui, because ui performance may seriously be affected by a peak in downloads or streaming. Instead, there is most often separate downlaod and streaming servers, and the two copies go to two different mounts, hence another reason not to use hard links. But as mentionend under 2), it is not possible anyway. On solution would be to write your own distribution handler wich puts a copy somewhere an then creates links to your set of distribution folders. Tobias On 17.09.2011, at 02:51, [email protected] wrote: > Hi, > > I know this has come up before, but I couldn't find discussion of the issue > or a > ticket so I'm hoping someone can point me to the right place. Our engage > instance is keeping three copies of each file, one in /downloads, one in > /streams, and one in /workspace. > > Can some of these directories be nuked without effecting functionality? > > Is a ticket open for the issue? > > We've got a fairly moderate system going right now (30 gig of lectures in > engage > if you count them once), but it's only the second week of a 14 week semester, > so > that's going to jump to around 210 gig by the end of term, which brings us to > just over half a terabyte. > > I wasn't planning on eating up this much space for that server for the whole > year... > > Chris > _______________________________________________ > Matterhorn-users mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users _______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
