rebar/test/upgrade_project/rel/files/vm.args

## Name of the node
-name dummy@127.0.0.1

## Cookie for distributed erlang
-setcookie dummy

## Heartbeat management; auto-restarts VM if it dies or becomes unresponsive
## (Disabled by default..use with caution!)
##-heart

## Enable kernel poll and a few async threads
##+K true
##+A 5

## Increase number of concurrent ports/sockets
##-env ERL_MAX_PORTS 4096

## Tweak GC to run more often
##-env ERL_FULLSWEEP_AFTER 10
Add 'generate-upgrade' command To support OTP release upgrades I have added support for building upgrade packages. Support for this is included in the rebar_upgrade module, specifically generate_upgrade/2. It requires one variable to be set on the command line 'previous_release' which is the absolute path or relative path from 'rel/' to the previous release one is upgrading from. Running an upgrade will create the needed files, including a relup and result in a tarball containing the upgrade being written to 'rel/'. When done it cleans up the temporary files systools created. Usage: $ rebar generate-upgrade previous_release=/path/to/old/version This also includes a dummy application that can be used to test upgrades as well as an example. Special thanks to Daniel Reverri, Jesper Louis Andersen and Richard Jones for comments and patches. 2011-01-27 17:15:25 +00:00			`## Name of the node`
			`-name dummy@127.0.0.1`

			`## Cookie for distributed erlang`
			`-setcookie dummy`

			`## Heartbeat management; auto-restarts VM if it dies or becomes unresponsive`
			`## (Disabled by default..use with caution!)`
			`##-heart`

			`## Enable kernel poll and a few async threads`
Sync test/upgrade_project/rel/files with priv/templates 2013-06-12 14:57:26 +00:00			`##+K true`
			`##+A 5`
Add 'generate-upgrade' command To support OTP release upgrades I have added support for building upgrade packages. Support for this is included in the rebar_upgrade module, specifically generate_upgrade/2. It requires one variable to be set on the command line 'previous_release' which is the absolute path or relative path from 'rel/' to the previous release one is upgrading from. Running an upgrade will create the needed files, including a relup and result in a tarball containing the upgrade being written to 'rel/'. When done it cleans up the temporary files systools created. Usage: $ rebar generate-upgrade previous_release=/path/to/old/version This also includes a dummy application that can be used to test upgrades as well as an example. Special thanks to Daniel Reverri, Jesper Louis Andersen and Richard Jones for comments and patches. 2011-01-27 17:15:25 +00:00
			`## Increase number of concurrent ports/sockets`
Sync test/upgrade_project/rel/files with priv/templates 2013-06-12 14:57:26 +00:00			`##-env ERL_MAX_PORTS 4096`
Add 'generate-upgrade' command To support OTP release upgrades I have added support for building upgrade packages. Support for this is included in the rebar_upgrade module, specifically generate_upgrade/2. It requires one variable to be set on the command line 'previous_release' which is the absolute path or relative path from 'rel/' to the previous release one is upgrading from. Running an upgrade will create the needed files, including a relup and result in a tarball containing the upgrade being written to 'rel/'. When done it cleans up the temporary files systools created. Usage: $ rebar generate-upgrade previous_release=/path/to/old/version This also includes a dummy application that can be used to test upgrades as well as an example. Special thanks to Daniel Reverri, Jesper Louis Andersen and Richard Jones for comments and patches. 2011-01-27 17:15:25 +00:00
			`## Tweak GC to run more often`
Sync test/upgrade_project/rel/files with priv/templates 2013-06-12 14:57:26 +00:00			`##-env ERL_FULLSWEEP_AFTER 10`