pman(3erl) [linux man page]

pman(3erl)						     Erlang Module Definition							pman(3erl)

NAME

       pman - A graphical process manager.

DESCRIPTION

       A  graphical  tool used to inspect the Erlang processes executing either locally or on remote nodes. It is also possible to trace events in
       the individual processes.

EXPORTS

       start()
       start(Excluded)
       start_notimeout()
       start_notimeout(Excluded)

	      Types  Excluded = [Module]
		     Module = atom()

	      Starts Pman. It will use the previously saved trace settings in HOME/.erlang_tools/pman.opts , where HOME is the user's home  direc-
	      tory, if such a file exists. Otherwise standard trace settings will be used. The return value should be ignored.

	      Excluded	is  a  list of module names. If the argument is present, processes currently executing in any of these modules will not be
	      shown by Pman.

	      start/0,1 will fail unless the start-up succeeds within 20 seconds, whereas start_notimeout/0,1 will wait indefinitely.

       proc(Process)
       proc(A, B, C)

	      Types  Process = pid() | atom()
		     A = B = C = integer()

	      Starts a Pman trace window for the specified process. The return value should be ignored.

	      The process to trace is given either by its pid or by its registered name. It is also possible to use proc/3 to trace the pid repre-
	      sented as <A,B,C> .

Ericsson AB							    pman 2.7.1								pman(3erl)

erl_boot_server(3erl)					     Erlang Module Definition					     erl_boot_server(3erl)

NAME

       erl_boot_server - Boot Server for Other Erlang Machines

DESCRIPTION

       This server is used to assist diskless Erlang nodes which fetch all Erlang code from another machine.

       This  server  is  used  to fetch all code, including the start script, if an Erlang runtime system is started with the -loader inet command
       line flag. All hosts specified with the -hosts Host command line flag must have one instance of this server running.

       This server can be started with the kernel configuration parameter start_boot_server .

       The erl_boot_server can both read regular files as well as files in archives. See code(3erl) and erl_prim_loader(3erl) .

   Warning:
       The support for loading of code from archive files is experimental. The sole purpose of releasing it before it is ready is to obtain  early
       feedback. The file format, semantics, interfaces etc. may be changed in a future release.

EXPORTS

       start(Slaves) -> {ok, Pid} | {error, What}

	      Types  Slaves = [Host]
		     Host = atom()
		     Pid = pid()
		     What = term()

	      Starts the boot server. Slaves is a list of IP addresses for hosts which are allowed to use this server as a boot server.

       start_link(Slaves) -> {ok, Pid} | {error, What}

	      Types  Slaves = [Host]
		     Host = atom()
		     Pid = pid()
		     What = term()()

	      Starts the boot server and links to the caller. This function is used to start the server if it is included in a supervision tree.

       add_slave(Slave) -> ok | {error, What}

	      Types  Slave = Host
		     Host = atom()
		     What = term()

	      Adds a Slave node to the list of allowed slave hosts.

       delete_slave(Slave) -> ok | {error, What}

	      Types  Slave = Host
		     Host = atom()
		     What = void()

	      Deletes a Slave node from the list of allowed slave hosts.

       which_slaves() -> Slaves

	      Types  Slaves = [Host]
		     Host = atom()

	      Returns the current list of allowed slave hosts.

SEE ALSO

       init(3erl) , erl_prim_loader(3erl)

Ericsson AB							   kernel 2.14.3					     erl_boot_server(3erl)