Certain configuration of SmartSVN has to be done by VM options, in files called
smartsvn.vmoptions: there is a global file which affects the entire installation, i.e. is applied to all users and a user-specific file which only affects the current user and overrides options from the global file. The location of both files depends on your operating system:
- Windows: the global file is
bin\smartsvn.vmoptionsin SmartSVN's installation directory; the local file is
%APPDATA%is the path defined in the environment variable
- Linux: the global file is
bin/smartsvn.vmoptionsin SmartSVN's installation directory; the local file is
- Mac: the global file is
Contents/MacOS/smartsvn.vmoptionsin SmartSVN's installation directory
SmartSVN.app; the local file is
Following VM options can be specified in either of these two files:
Location of the Settings Directory
The settings contains SmartSVN's settings. See Installation and Files for information about the default location and contents of the settings directory. On Windows and Linux, you can change its location by modifying the VM option
Changing the settings directory's location is not supported on Mac OS X.
Within the value of
smartsvn.settings, certain Java system properties are allowed, such as
user.home. Another accepted value is the special
smartsvn.installation property, which refers to the SmartSVN installation directory.
Location of the Updates Directory
The Updates directory contains downloaded program updates. See Installation and Files for information about the default location and contents of the Updates directory. On Windows and Linux, you can change its location by modifying the VM option
Used Java Runtime Environment
Use the Windows environment variable
SMARTSVN_JAVA_HOME to tell SmartSVN which JRE to use.
On Linux, you can configure the JRE to be used by adding
The memory limit (also known as maximum heap size) specifies how much RAM the SmartSVN process is allowed to use. The memory limit can be configured by the VM option
If the set value is too low, SmartSVN may run out of memory during memory-intensive operations.
32-Bit Java VMs only allow to configure a maximum memory limit of roughly
1200M. For almost all setups and repository sizes, this should be sufficient. If not, this usually indicates a problem, thus please contact us at firstname.lastname@example.org.