From b075fbda0ad0a711344011fb365b00acd5b64760 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B6rn=20Gustavsson?= Date: Wed, 3 Apr 2019 13:20:37 +0200 Subject: Fix broken links A multitude of broken links were found when a bug was fixed in the link checker. --- lib/jinterface/doc/src/jinterface_users_guide.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'lib/jinterface') diff --git a/lib/jinterface/doc/src/jinterface_users_guide.xml b/lib/jinterface/doc/src/jinterface_users_guide.xml index 56f88124bf..504c77f339 100644 --- a/lib/jinterface/doc/src/jinterface_users_guide.xml +++ b/lib/jinterface/doc/src/jinterface_users_guide.xml @@ -366,20 +366,20 @@ OtpNode node = new OtpNode("gurka"); OtpEpmd class. Nodes wishing to contact other nodes must first request information from Epmd before a connection can be set up, however this is done automatically - by OtpSelf.connect() when necessary.

-

When you use OtpSelf.connect() to connect to an Erlang node, + by OtpSelf.connect() when necessary.

+

When you use OtpSelf.connect() to connect to an Erlang node, a connection is first made to epmd and, if the node is known, a connection is then made to the Erlang node.

Java nodes can also register themselves with epmd if they want other nodes in the system to be able to find and connect to them. - This is done by call to method OtpEpmd.publishPort().

+ This is done by call to method OtpEpmd.publishPort().

Be aware that on some systems (such as VxWorks), a failed node will not be detected by this mechanism since the operating system does not automatically close descriptors that were left open when the node failed. If a node has failed in this way, epmd will prevent you from registering a new node with the old name, since it thinks that the old name is still in use. In this case, you must unregister the name - explicitly, by using OtpEpmd.unPublishPort()

+ explicitly, by using OtpEpmd.unPublishPort()

This will cause epmd to close the connection from the far end. Note that if the name was in fact still in use by a node, the results of this operation are unpredictable. Also, doing this does not cause the -- cgit v1.2.3