[erlang-questions] Using erl_call
Kenneth Lundin
kenneth.lundin@REDACTED
Mon Feb 18 13:27:51 CET 2008
Of course you need to have the correct path setup in order to find erl_call.
But I think it is really questionable why you should execute erl_call
at all from a C-node as you call it.
A C-node is for me a C-program communicationg with other Erlang-nodes
and C-nodes using the Erlang distribution Protocol. The C-node is
implemented with help of the ei and erl_interface library functions
which are available in the erl_interface
application.
Erl_call is a C-program that acts as a temporary short lived C-node. Erl_call
is written using the erl_interface functions mentioned above and was originally
meant to be an example of how to use these functions to implement a C-node.
So if you already have a C-node you don't need to execute erl_call. You can
look at the erl_call source code and do something similar in your own C-node
if you have not already implemented functionality for invoking a function on
an Erlang-node from a C-node.
/Kenneth , Erlang/OTP team at Ericsson
On 2/18/08, Anthony Kong <anthony.hw.kong@REDACTED> wrote:
> Can You specify full path?
>
> e.g. assuming *nix based OS,
>
> system("/usr/bin/erl_call ...");
>
>
> 2008/2/18 J Bhanot <j.bhanot@REDACTED>:
> >
> > Hi,
> >
> > How can we use erl_call in C node.
> >
> > I have tried using system("erl_call -s -a 'erlang time' -n e1");
> >
> > but, get the error sh: erl_call: command not found
> >
> > guess because its not shell command....
> >
> > Is there any other way of doing this.
> >
> > Regards,
> >
> > jb____________________________________________=====-----=====-----=====
> > Notice: The information contained in this e-mail
> > message and/or attachments to it may contain
> > confidential or privileged information. If you are
> > not the intended recipient, any dissemination, use,
> > review, distribution, printing or copying of the
> > information contained in this e-mail message
> > and/or attachments to it are strictly prohibited. If
> > you have received this communication in error,
> > please notify us by reply e-mail or telephone and
> > immediately and permanently delete the message
> > and any attachments. Thank you
> >
> >
> >
> >
> > _______________________________________________
> > erlang-questions mailing list
> > erlang-questions@REDACTED
> > http://www.erlang.org/mailman/listinfo/erlang-questions
> >
>
>
>
> --
> /*--*/
> Don't EVER make the mistake that you can design something better than
> what you get from ruthless massively parallel trial-and-error with a
> feedback cycle. That's giving your intelligence _much_ too much
> credit.
>
> - Linus Torvalds
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions
>
More information about the erlang-questions
mailing list