19962009 Ericsson AB. All Rights Reserved. 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. erl_call Torbjörn Törnkvist Torbjörn Törnkvist Bjarne Däcker Torbjörn Törnkvist 97-05-16 B erl_call.sgml
erl_call Call/Start a Distributed Erlang Node

makes it possible to start and/or communicate with a distributed Erlang node. It is built upon the library as an example application. Its purpose is to use an Unix shell script to interact with a distributed Erlang node. It performs all communication with the Erlang rex server, using the standard Erlang RPC facility. It does not require any special software to be run at the Erlang target node.

The main use is to either start a distributed Erlang node or to make an ordinary function call. However, it is also possible to pipe an Erlang module to and have it compiled, or to pipe a sequence of Erlang expressions to be evaluated (similar to the Erlang shell).

Options, which cause to be read, can be used with advantage as scripts from within (Unix) shell scripts. Another nice use of could be from (http) CGI-bin scripts.

 erl_call <options> Start/Call Erlang

Each option flag is described below with its name, type and meaning.

-a [Mod [Fun [Args]]]]

(optional): Applies the specified function and returns the result. must be specified, however [] is assumed for unspecified and . should be in the same format as for . Note that this flag takes exactly one argument, so quoting may be necessary in order to group , and , in a manner dependent on the behavior of your command shell.

 -c Cookie

(optional): Use this option to specify a certain cookie. If no cookie is specified, the file is read and its content are used as cookie. The Erlang node we want to communicate with must have the same cookie.

 -d

(optional): Debug mode. This causes all IO to be output to the file , where is the node name of the Erlang node in question.

 -e

(optional): Reads a sequence of Erlang expressions, separated by ',' and ended with a '.', from until EOF (Control-D). Evaluates the expressions and returns the result from the last expression. Returns if successful.

 -h HiddenName

(optional): Specifies the name of the hidden node that represents.

 -m

(optional): Reads an Erlang module from and compiles it.

 -n Node

(one of is required): Has the same meaning as and can still be used for backwards compatibility reasons.

 -name Node

(one of is required): is the name of the node to be started or communicated with. It is assumed that is started with , which means that fully qualified long node names are used. If the option is given, an Erlang node will (if necessary) be started with .

 -q

(optional): Halts the Erlang node specified with the -n switch. This switch overrides the -s switch.

 -r

(optional): Generates a random name of the hidden node that represents.

 -s

(optional): Starts a distributed Erlang node if necessary. This means that in a sequence of calls, where the '' and '' are constant, only the first call will start the Erlang node. This makes the rest of the communication very fast. This flag is currently only available on the Unix platform.

 -sname Node

(one of is required): is the name of the node to be started or communicated with. It is assumed that is started with which means that short node names are used. If option is given, an Erlang node will be started (if necessary) with .

 -v

(optional): Prints a lot of information. This is only useful for the developer and maintainer of .

 -x ErlScript

(optional): Specifies another name of the Erlang start-up script to be used. If not specified, the standard start-up script is used.
Examples

Starts an Erlang node and calls .

Terminates an Erlang node by calling .

An apply with several arguments.

Evaluates a couple of expressions. The input ends with EOF (Control-D).

Compiles a module and runs it. Again, the input ends with EOF (Control-D). (In the example shown, the output has been formatted afterwards).

P = processes(), F = fun(X) -> {X,process_info(X,registered_name)} end, lists:map(F,[],P). ^D [{, {registered_name,init}}, {, {registered_name,erl_prim_loader}}, {, {registered_name,error_logger}}, {, {registered_name,application_controller}}, {, {registered_name,kernel}}, {, []}, {, {registered_name,kernel_sup}}, {, {registered_name,net_sup}}, {, {registered_name,net_kernel}}, {, []}, {, {registered_name,global_name_server}}, {, {registered_name,auth}}, {, {registered_name,rex}}, {, []}, {, {registered_name,file_server}}, {, {registered_name,code_server}}, {, {registered_name,user}}, {, []}] ]]>