<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>I will admit that I haven't been following this thread - apologies. Also, I have yet to update my old knowledge of how to do this to understand how it's done using reltool et al.</div><div><br></div><div>You can use a releases/ directory outside the OTP root. </div><div><br></div><div>When you build the boot script, use the {variables, Vars} option, and when starting, define the variables using the -boot_var command-line option.</div><div><br></div><div><a href="http://www.erlang.org/doc/man/systools.html#make_script-2">http://www.erlang.org/doc/man/systools.html#make_script-2</a></div><div><br></div><div>E.g. {variables, [{"MYROOT", PathToMyRoot}, {"OTP_ROOT", ERL_TOP}]}</div><div><br></div><div>init:get_argument(root) should point to the place where you have your .rel and .boot files etc. This can be entirely separate from where you keep your lib/ roots.</div><div><br></div><div><a href="http://www.erlang.org/doc/embedded/embedded_solaris.html">http://www.erlang.org/doc/embedded/embedded_solaris.html</a></div><div><br></div><div>chapter 1.4, can be a good place to read up on how to get Erlang started with full control over the various variables. Perhaps also:</div><div><br></div><div><a href="http://www.erlang.org/doc/system_principles/create_target.html">http://www.erlang.org/doc/system_principles/create_target.html</a></div><div><br></div><div>BR,</div><div>Ulf W</div><br><div><div>On 23 Apr 2011, at 19:21, Per Melin wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Sat, Apr 23, 2011 at 4:41 PM, Pablo Platt <<a href="mailto:pablo.platt@yahoo.com">pablo.platt@yahoo.com</a>> wrote:<br><blockquote type="cite">Again, the errors I'm getting are:<br></blockquote><blockquote type="cite">1. Error when trying to use release_handler:unpack_release("myserver_2"):<br></blockquote><blockquote type="cite">{error,{enoent,"/usr/lib/myserver/releases/myserver_2.rel"}}<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">2. After I copy myserver_2.rel manually to /usr/lib/myserver/releases and<br></blockquote><blockquote type="cite">trying release_handler:unpack_release("myserver_2") again I'm getting:<br></blockquote><blockquote type="cite">{error,{{case_clause,{error,eacces}},<br></blockquote><blockquote type="cite"> [{release_handler,extract_tar,2},<br></blockquote><blockquote type="cite"> {release_handler,do_unpack_release,4},<br></blockquote><blockquote type="cite"> {release_handler,handle_call,3},<br></blockquote><blockquote type="cite"> {gen_server,handle_msg,5},<br></blockquote><blockquote type="cite"> {proc_lib,init_p_do_apply,3}]}}<br></blockquote><br>Pablo and I went off-list for a while. I'll recap what we discovered.<br><br>release_handler uses init:get_argument(root) as the base directory for<br>some of its operations. When ERTS is included (which it probably must<br>be) in the release that is not a problem, but since it was not<br>included here and beam was started from the standard installation, the<br>root is /usr/local/lib/erlang.<br><br>As far as I can tell, release_handler doesn't seem to deal well with a<br>release directory that is outside of $OTP_ROOT. There is a SASL<br>environment variable called releases_dir which release_handler<br>sometimes honors, and sometimes ignores (if I'm reading it right).<br>_______________________________________________<br>erlang-questions mailing list<br><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>http://erlang.org/mailman/listinfo/erlang-questions<br></div></blockquote></div><br><div>
<div>Ulf Wiger, CTO, Erlang Solutions, Ltd.</div><div><a href="http://erlang-solutions.com">http://erlang-solutions.com</a></div><div><br></div><br class="Apple-interchange-newline">
</div>
<br></body></html>