[erlang-questions] problem with global registration

Ulf Wiger (TN/EAB) <>
Tue Nov 7 20:45:24 CET 2006


Make sure your nodes have a chance to connect
before running debugctrl().

Global will not synchronize the global registry 
until the nodes have connected. Before that, 
your name lookup will fail, unless the globally
registered process is running in the same node
as the caller.

A single message to the other node, or an rpc:call()
will do.

BR,
Ulf W

> -----Original Message-----
> From: Garry Hodgson [mailto:] 
> Sent: den 7 november 2006 20:35
> To: Ulf Wiger (TN/EAB); Erlang
> Subject: Re: RE: [erlang-questions] problem with global registration
> 
> "Ulf Wiger \(TN/EAB\)" <> wrote:
> 
> > Where does your global server 'util' start?
> 
> the main server process, running on node "main", calls util:start().  
> after it's been running a while, happily logging messages, i 
> run the other program, with the "-run master debugctrl on".  
> this runs on same machine, as node "debug".
> 
> > When you call debugctrl() using the -run argument, the call will be 
> > dispatched pretty early.
> 
> but i have the same problem if i run erlang by hand:
> 
>     $ erl -sname debug -setcookie keebler 
>     Erlang (BEAM) emulator version 5.3.6.3 [source] [hipe] [threads:0]
> 
>     Eshell V5.3.6.3  (abort with ^G)
>     ()1> master:debugctrl( ["on"] ).
>     ** exited: 
> {noproc,{gen_server,call,[{global,util},{enable,debug},10000]}} **
>     ()2>  
> 
> 
> ----
> Garry Hodgson, Senior Software Geek, AT&T CSO
> 
> But I'm not giving in an inch to fear
> 'Cause I promised myself this year
> I feel like I owe it...to someone.
> 
> 




More information about the erlang-questions mailing list