[erlang-bugs] order of the parameters for erl on Windows

Mickael Remond <>
Tue Sep 12 11:08:22 CEST 2006


Hello,

it seems to me that the order of the command-line parameter (erl and
werl) on Microsoft Windows is important.
When having a complex command-line, if I put the -sname parameter first,
the erl emulator ignore it and do not start in networked mode.

Example:
erl.exe sname  -detached -env ERL_MAX_PORT=32000 -env EJABBERD_MSGS_PATH
"../lib/ejabberd-1.1.1/priv/msgs/" -env EJABBERD_CONFIG_PATH
"../conf/ejabberd.cfg" -env EJABBERD_SO_PATH
"../lib/ejabberd-1.1.1/priv/lib/windows/" -env EJABBERD_LOG_PATH
"../logs/ejabberd.log" -kernel inetrc '"../conf/inetrc.win"' -mnesia dir
'"../database/default"' -sasl sasl_error_logger
{file,"../logs/sasl.log"} -setcookie test 
-s ejabberd

If I put this option at the end of the line, this is working as
expected:
erl.exe -detached -env ERL_MAX_PORT=32000 -env EJABBERD_MSGS_PATH
"../lib/ejabberd-1.1.1/priv/msgs/" -env EJABBERD_CONFIG_PATH
"../conf/ejabberd.cfg" -env EJABBERD_SO_PATH
"../lib/ejabberd-1.1.1/priv/lib/windows/" -env EJABBERD_LOG_PATH
"../logs/ejabberd.log" -kernel inetrc '"../conf/inetrc.win"' -mnesia dir
'"../database/default"' -sasl sasl_error_logger
{file,"../logs/sasl.log"} -sname  -setcookie test 
-s ejabberd

I have not seen this behaviour on Linux.
Is it a known behaviour on Windows ?

Thank you !

-- 
Mickaël Rémond
 http://www.process-one.net/




More information about the erlang-bugs mailing list