@@ -65,14 +65,14 @@ arguments_:
65
65
_ Examples:_
66
66
67
67
``` erlang
68
- % erl +W w -sname arnie +R 9 -s my_init -extra +bertie
68
+ % erl +W w -sname arnie +S 2 -s my_init -extra +bertie
69
69
(arnie@host )1 > init :get_argument (sname ).
70
70
{ok ,[[" arnie" ]]}
71
71
(arnie@host )2 > init :get_plain_arguments ().
72
72
[" +bertie" ]
73
73
```
74
74
75
- Here ` +W w ` and ` +R 9 ` are emulator flags. ` -s my_init ` is an init flag,
75
+ Here ` +W w ` and ` +S 2 ` are emulator flags. ` -s my_init ` is an init flag,
76
76
interpreted by ` init ` . ` -sname arnie ` is a user flag, stored by ` init ` . It is
77
77
read by Kernel and causes the Erlang runtime system to become distributed.
78
78
Finally, everything after ` -extra ` (that is, ` +bertie ` ) is considered as plain
@@ -856,21 +856,6 @@ behavior of earlier flags.
856
856
On Windows the default value is set to ` 8196 ` because the normal OS
857
857
limitations are set higher than most machines can handle.
858
858
859
- - ** ` +R ReleaseNumber ` {: #compat_rel }** - Sets the compatibility mode.
860
-
861
- The distribution mechanism is not backward compatible by default. This flag
862
- sets the emulator in compatibility mode with an earlier Erlang/OTP release
863
- ` ReleaseNumber ` . The release number must be in the range
864
- ` <current release>-2 ` through ` <current release> ` . This limits the emulator,
865
- making it possible for it to communicate with Erlang nodes (as well as C
866
- and Java nodes) running that earlier release.
867
-
868
- > #### Note {: .info }
869
- >
870
- > Ensure that all nodes (Erlang-, C-, and Java nodes) of a distributed Erlang
871
- > system is of the same Erlang/OTP release, or from two different Erlang/OTP
872
- > releases X and Y, where _ all_ Y nodes have compatibility mode X.
873
-
874
859
- ** ` +r ` ** - Forces ETS memory blocks to be moved on reallocation.
875
860
876
861
- ** ` +rg ReaderGroupsLimit ` {: #+rg }** - Limits the number of reader groups used
0 commit comments