File: orber_help.txt

package info (click to toggle)
erlang 1%3A19.2.1%2Bdfsg-2%2Bdeb9u3
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 175,856 kB
  • sloc: erlang: 1,414,205; xml: 397,681; ansic: 345,439; cpp: 51,554; makefile: 23,040; java: 11,480; sh: 10,128; lisp: 9,231; python: 4,853; pascal: 3,273; perl: 2,970; asm: 2,900; javascript: 700; tcl: 245; sed: 86
file content (42 lines) | stat: -rw-r--r-- 916 bytes parent folder | download | duplicates (11)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42



		Help for the Orber administration tool
		--------------------------------------





	The purpose of this tool is to supply an easy way to 
        access Orber nodes and via a GUI explore:
          - NameService
          - Configuration settings
          - Interface Repository

	All nodes that are known to this tool is shown in the node
	window, normally this is all Erlang nodes visible with the
	[node()|nodes()] commands.


The Node window
---------------

	The node window monitor nodes. 


Technical Detail
----------------

	Trouble shooting
	----------------

	Q. Why doesn't all my nodes show up in the node window?

	A. Are the nodes visible with the [node()|nodes()] commands 
        in the shell? If not you must do net:ping(NodeName) to add
        nodes to the Erlang distribution.

	Q. When trying to access a node I get no valid response?

	A. Make sure that Orber is running on the node.