blob: 8fe723ba83d1093ec09228ea9f2fdee4aa04e4a0 (
plain) (
tree)
|
|
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE chapter SYSTEM "chapter.dtd">
<chapter>
<header>
<copyright>
<year>2013</year><year>2014</year>
<holder>Ericsson AB. All Rights Reserved.</holder>
</copyright>
<legalnotice>
The contents of this file are subject to the Erlang Public License,
Version 1.1, (the "License"); you may not use this file except in
compliance with the License. You should have received a copy of the
Erlang Public License along with this software. If not, it can be
retrieved online at http://www.erlang.org/.
Software distributed under the License is distributed on an "AS IS"
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
the License for the specific language governing rights and limitations
under the License.
</legalnotice>
<title>Introduction</title>
<prepared>Lukas Larsson</prepared>
<docno></docno>
<date>2014-01-08</date>
<rev>A</rev>
<file>ose_intro.xml</file>
</header>
<section>
<title>Features</title>
</section>
<section>
<title>run_erl and to_erl</title>
<p>
In OSE run_erl and to_erl are combined into a single load module called
run_erl_lm. Installing and starting the load module will add two new
shell commands called run_erl and to_erl. They work in exactly the same
way as the unix variants of run_erl and to_erl, except that the read
and write pipes have to be placed under the /pipe vm. One additional
option also exists to run_erl on ose:
<taglist>
<tag><c>-block Name</c></tag>
<item>The name of the install handle and block that will be created/used by
installing and exectuting the first part of the command. If nothing
if given the basename of the load module will be used for this value.
Example:
<code>pm_install erlang /path/to/erlang/vm
run_erl -daemon -block erlang /pipe/ /mst/erlang_logs/ "erl -A 10"</code>
</item>
</taglist>
See also
<seealso marker="erts:run_erl">run_erl</seealso> for more details.
</p>
</section>
</chapter>
|
