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)
Check Out this Related Man Page
erl_internal(3erl) Erlang Module Definition erl_internal(3erl)NAME
erl_internal - Internal Erlang Definitions
DESCRIPTION
This module defines Erlang BIFs, guard tests and operators. This module is only of interest to programmers who manipulate Erlang code.
EXPORTS
bif(Name, Arity) -> bool()
Types Name = atom()
Arity = integer()
Returns true if Name/Arity is an Erlang BIF which is automatically recognized by the compiler, otherwise false .
guard_bif(Name, Arity) -> bool()
Types Name = atom()
Arity = integer()
Returns true if Name/Arity is an Erlang BIF which is allowed in guards, otherwise false .
type_test(Name, Arity) -> bool()
Types Name = atom()
Arity = integer()
Returns true if Name/Arity is a valid Erlang type test, otherwise false .
arith_op(OpName, Arity) -> bool()
Types OpName = atom()
Arity = integer()
Returns true if OpName/Arity is an arithmetic operator, otherwise false .
bool_op(OpName, Arity) -> bool()
Types OpName = atom()
Arity = integer()
Returns true if OpName/Arity is a Boolean operator, otherwise false .
comp_op(OpName, Arity) -> bool()
Types OpName = atom()
Arity = integer()
Returns true if OpName/Arity is a comparison operator, otherwise false .
list_op(OpName, Arity) -> bool()
Types OpName = atom()
Arity = integer()
Returns true if OpName/Arity is a list operator, otherwise false .
send_op(OpName, Arity) -> bool()
Types OpName = atom()
Arity = integer()
Returns true if OpName/Arity is a send operator, otherwise false .
op_type(OpName, Arity) -> Type
Types OpName = atom()
Arity = integer()
Type = arith | bool | comp | list | send
Returns the Type of operator that OpName/Arity belongs to, or generates a function_clause error if it is not an operator at all.
Ericsson AB stdlib 1.17.3 erl_internal(3erl)
I've been asked to implement the NetIQ Unix Agent on some production database servers running Solaris 10 and wanted to check with the community and see what type of results you've seen.
A review of the documents seems to indicate that this agent can't connect to the standard Windows Management... (3 Replies)