Tue Feb 26 22:13:03 CET 2013
On Tue, Feb 26, 2013 at 8:39 PM, Erik Reitsma <> wrote:
> Hi David & others,
> I intend to solve this by making it possible to provide extra command line
> arguments to erl when Erlang is started from SL4A. Unfortunately I cannot
> set this from SL4A, unless I modify SL4A, which I would very much like to
> avoid. So, I have to set the command line arguments from the Erlang
> installer. This means however, that all started shells will be started with
> the same command line arguments. So, either all start with distribution, or
> without, unless you change the command line arguments between two starts. I
> have tried this, and I can start a shell with arguments "-sname x -setcookie
> ssssssss" (no need for a cookie file this way!).
> Would this be an acceptable solution for you?
Maybe you can control environment variables instead? These are
equivalent to command-line arguments.
ERL_FLAGS, ERL_AFLAGS, ERL_ZFLAGS
If not, I would go for non-distributed approach, given that users can
"go distributed" by themselves.
Erlang R15B02 (erts-5.9.2) [source] [smp:2:2] [async-threads:0]
Eshell V5.9.2 (abort with ^G)
1> net_kernel:start(['', longnames]).
()2> erlang:set_cookie(node(), yadda).
More information about the erlang-questions