Distributed Erlang embeded startup problem

[Eranga Udesh]

Hi,

I have created a target system. It's a distributed system, having 2
optional nodes, if one failes application failover to the other node.
If the high priority node comes alive it takes over.

Attached files are,
sys.config - configuration file in one node. The other node's file
just have the name of this node in "sync_nodes_optional"
esme.system - Linux init file

The init file is located at /etc/rc.d/init.d and in linked to
/etc/rc.d/rc3.d/S91esme.system

When I ran init files manually, the system starts well. When a node
fails, it fall backs and everything works smoothly.

But when I restart both systems, once they come up, I see both are
running the same application.

When I ran the nodes() in one node, I can see that it has connected to
other node too.

What puzzeling me is, why it runs correctly when I ran manually and
why it doesn't in a system reboot.

Please help.

Thanks in advance,
- Eranga
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sys.config
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20050630/b73fc395/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: esme.system
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20050630/b73fc395/attachment-0001.ksh>