OpenSUSE 13.1: Difference between revisions

Line 8:

* If you turn the firewall off during the installation, the firewall will not stay off even though it says it will. '''Solution:''' Wait until openSUSE has installed and during configuration, turn it off again. Alternatley, turn the firewall off with YaST after installation and also disallow it from starting at startup.

* CrashPlan will need OpenJDK uninstalled (requiring a few Libreoffice extensions to be uninstalled also). Download the latest JRE from Oracle to make it work. You will also need to include a line in <code>/usr/local/crashplan/bin/run.conf</code>. See [[CrashPlan client closes in some Linux installations]].

* CrashPlan will also need the memory allocation changing if backing up more than 1TB. In the same file as above, find <code>-Xmx512</code> and change to at least <code>-Xmx1024</code> or more, otherwise CrashPlan will run out of memory and keep restarting without backing up.

* CrashPlan will also need the memory allocation changing if backing up more than 1TB. In the same file as above, find <code>-Xmx512</code> and change to at least <code>-Xmx1024</code> or more (Recommended: <code>-Xmx2048</code>), otherwise CrashPlan will run out of memory and keep restarting without backing up.

== Information ==

@@ Line 8: / Line 8: @@
 * If you turn the firewall off during the installation, the firewall will not stay off even though it says it will. '''Solution:''' Wait until openSUSE has installed and during configuration, turn it off again. Alternatley, turn the firewall off with YaST after installation and also disallow it from starting at startup.
 * CrashPlan will need OpenJDK uninstalled (requiring a few Libreoffice extensions to be uninstalled also). Download the latest JRE from Oracle to make it work. You will also need to include a line in <code>/usr/local/crashplan/bin/run.conf</code>. See [[CrashPlan client closes in some Linux installations]].
-* CrashPlan will also need the memory allocation changing if backing up more than 1TB. In the same file as above, find <code>-Xmx512</code> and change to at least <code>-Xmx1024</code> or more, otherwise CrashPlan will run out of memory and keep restarting without backing up.
+* CrashPlan will also need the memory allocation changing if backing up more than 1TB. In the same file as above, find <code>-Xmx512</code> and change to at least <code>-Xmx1024</code> or more (Recommended: <code>-Xmx2048</code>), otherwise CrashPlan will run out of memory and keep restarting without backing up.
 == Information ==