blob: 9e88635b0918fbefa20bf46210f0496785e701e4 [file] [log] [blame]
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="copyright" content="Copyright (c) IBM Corporation, Red Hat, and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page."/>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
<meta http-equiv="Content-Style-Type" content="text/css"/>
<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"/>
<title>Minimizing data loss from crashes</title>
</head>
<body bgcolor="#ffffff">
<h1 class="Head">Minimizing data loss from crashes</h1>
<p class="Intro">
The Workbench periodically saves a snapshot in order to reduce the risk of
losing data due to crashes.
The default period between saves is 5 minutes, but you can change this
from the <a href="ref-9.htm">Workspace preferences page</a>
(<b>Window &gt; Preferences &gt; General &gt; Workspace</b>).
From that page you can also set Eclipse to save all modified resources before
a manual build.
</p>
<p>Previously created projects and saved editor data are never lost as they are
written to disk immediately upon save. However, there is a risk of data loss in these areas:
</p>
<ul class="UnorderedList">
<li class="Item">
Unsaved data in open editors may be lost, depending on the editor implementation.</li>
<li class="Item">
Bookmarks and tasks might be lost.</li>
<li class="Item">
If a crash occurs during CVS synchronization, the Workbench may be out of sync.
You can check by performing the synchronize operation again.</li>
</ul>
<p>Developers of plug-ins can also choose to participate in the autosave
lifecycle and have the Workbench also save the state of their plug-ins.
See "<b><i>Workspace save participation</i></b>" in the
<b><i>Platform Plug-in Development Guide</i></b> for details.
</p>
<pre>
&lt;enablement&gt;
&lt;systemTest property="osgi.os" value="linux"/&gt;
&lt;/enablement&gt;
</pre>
<h2>Restarting after a crash on Linux</h2>
<p>After a crash you may find that Eclipse will not open because it
has (erroneously) detected that your workspace is in use.
To remedy this, enter:
</p>
<pre>
rm workspace/.metadata/.lock
</pre>
<p>You can now restart Eclipse.</p>
<p><img border="0" src="../images/ngrelr.png" alt="Related reference"/>
<br/><a href="ref-9.htm">Workspace preferences page</a>
</p>
</body>
</html>