[erlang-questions] erl_global_register/3 fails on NetBSD 4.0 - socket configuration?

[Raphael Langerhorst]

Hi all,

I just registered to this list, so hello everyone.

I'm using erl_interface to write C code that I can use in Erlang. The code can be found here:

http://raphael.g-system.at/secret/erl/cn.c

This happens with R11 and R12B-3 (which is erl_interface-3.5.7). This is on NetBSD.

An Erlang shell is started with "erl -sname xyz" on the host "nirvana".

After the shell has started, I run the C code. A connection to the erlang node is established (which succeeds), then the c node is published (which succeeds) and finally I want to register the C process to globals with erl_global_register/3 (which fails).

However, this last step fails and I have not been able to figure out why.

There is one curiousity. If you look at the code, a message loop ist started. Within this message loop I immediately receive the message

{rex,yes}

which suspiciously looks like a confirmation for registration. So, I think there may be something wrong with the socket settings (see socket setup function) which makes the erl_global_register/3 function miss the response from epmd?

What are the settings the socket should have? Anything specific? Do you see any other reason why erl_global_register fails?

Many thanks in advance!!
Raphael

-- 
Psssst! Schon das coole Video vom GMX MultiMessenger gesehen?
Der Eine für Alle: http://www.gmx.net/de/go/messenger03