On 12/25/2011 1:55 AM, Tobias Wunden wrote:
> The configuration in config.properties currently specifies several
> directories to live in ${java.io.tmpdir}, a directory which is set by the
> java virtual machine but can be overwritten at startup time
> (-Djava.io.tmpdir=). On some systems, that tmp directory will automatically
> be set to a location that is automatically being cleaned up upon restart,
> leading to a loss of data as Matterhorn stores the default database, the
> working file repository, the workspace and other data there.
>
> Even though this setup perfectly suits test installations (no need to fiddle
> with write permissions, as tmp directories are usually writable to every
> user), people keep running into this issue and wondering where their data
> went.
>
> As discussed at the last dev meeting, I propose to define the matterhorn tmp
> directory to be $FELIX_HOME/tmp. Please let me know if you see issues with
> this proposal, otherwise I am going to implement that change for 1.3.x [1]
Can we rename that to something more permanent sounding?
$FELIX_HOME/tmp sounds to me like something I could clear frequently,
like felix-cache. How about $FELIX_HOME/work?
G
> Tobias
>
> [1] http://opencast.jira.com/browse/MH-8455
> _______________________________________________
> Matterhorn mailing list
> [email protected]
> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>
>
> To unsubscribe please email
> [email protected]
> _______________________________________________
>
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
