aboutsummaryrefslogtreecommitdiffstats
path: root/lib/toolbar
diff options
context:
space:
mode:
authorSiri Hansen <[email protected]>2011-10-13 11:53:51 +0200
committerSiri Hansen <[email protected]>2011-11-17 16:47:28 +0100
commitbe04ed7beceeb4bcf5db7807e86df87e28c9f4b9 (patch)
tree3c5feabbfb50156cfc6e8025d9c20dd786fb9cd0 /lib/toolbar
parent1dec251ad333045847b75b8ee75d4bff4237108e (diff)
downloadotp-be04ed7beceeb4bcf5db7807e86df87e28c9f4b9.tar.gz
otp-be04ed7beceeb4bcf5db7807e86df87e28c9f4b9.tar.bz2
otp-be04ed7beceeb4bcf5db7807e86df87e28c9f4b9.zip
Distinguish restart_new_emulator from restart_emulator in upgrade instructions
Earlier, there was only one valid instruction to restart the emulator in an appup/relup script, 'restart_new_emulator'. A new instuction, 'restart_emulator', is now added, and the meaning is as follows: 'restart_new_emulator' is mainly for the core applications (erts, kernel, stdlib and sasl), and it indicates that there is new core functionality in the release and the emulator needs to be restarted before executing the upgrade scripts. If this instruction exists, a temporary release will be created which consists of the new version erts, kernel, stdlib and sasl, and the old versions of all other applications. After restarting the emulator with this temporary release, the rest of the upgrade instructions are executed, including loading of new versions. 'restart_emulator' can be used by any application if a restart of the emulator is needed after the upgrade instructions have been executed. In this case, the emulator will be restarted with the new release (i.e. not a tempoarary one) after all other upgrade instructions for all applications have been excecuted.
Diffstat (limited to 'lib/toolbar')
0 files changed, 0 insertions, 0 deletions