inviso_as_lib(3erl) [linux man page]

inviso_as_lib(3erl)					     Erlang Module Definition					       inviso_as_lib(3erl)

NAME

       inviso_as_lib - The Inviso Autostart Utility Library

DESCRIPTION

       The purpose of the Inviso autostart utility library is to facilitate the creation and modification of autostart configuration files used by
       the standard autostart.

EXPORTS

       setup_autostart(Node, R, Opts, TracerData, CmdFiles, Bindings, Transl, RTtag) -> ok | {error, Reason}

	      Types  Node = atom()
		     R = int()
		     Opts -- see inviso:add_nodes/2,3
		     TracerData -- see inviso:init_tracing/1,2
		     CmdFiles = [CmdFile]
		     CmdFile = string()
		     Bindings = [{Var,Val}]
		     Var = atom()
		     Val = term()
		     Transl = [{{M1,F1,Arity}, {M2,F2,{Mt,Ft}}}]
		     M1 = F1 = M2 = F2 = Mt = Ft = atom()
		     Arity = int()
		     RTtag = term()
		     Reason = term()

	      Creates an autostart configuration file on Node . The name of the file is automatically deducted from consulting	the  Runtime_Tools
	      configuration parameters at Node .

	      R is the number of allowed autostarts remaining.

	      Opts is the options which shall be given to the runtime component. See inviso:add_nodes/2,3 .

	      TracerData is used when initiating tracing on this node. See inviso:init_tracing/1,2 .

	      CmdFiles	points	out files containing instructions understood by the inviso_autostart_server implementation of an autostart initia-
	      tor.

	      Bindings is a list of {Var, Val} tuples, where Var is the name of a variable and Val the actual value of the variable.

	      Transl means that M1:F1/Arity shall be translated into M2:F2 .

	      RTtag is the incarnation tag of the runtime component. See See inviso:add_nodes/2,3 .

       set_repeat(Node, R) -> ok | {error, Reason}

	      Types  Node = atom()
		     R = int()
		     Reason = term()

	      Sets the repeat parameter in the autostart file at Node without changing any of its other contents. The autostart configuration file
	      must exist.

	      R is the number of allowed autostarts remaining.

       inhibit_autostart(Node) -> ok | {error, Reason}

	      Types  Node = atom()
		     Reason = term()

	      Sets the repeat parameter in the autostart file at Node to 0. Equivalent to set_repeat(Node, 0) .

Ericsson AB							   inviso 0.6.2 					       inviso_as_lib(3erl)

inviso_rt_meta(3erl)					     Erlang Module Definition					      inviso_rt_meta(3erl)

NAME

       inviso_rt_meta - Direct API to the Inviso Runtime Component's meta tracer

DESCRIPTION

       This module provides a direct API to the inviso meta tracer. These functions are only meant to be used in meta tracing CallFunc and Remove-
       Func .

       It can sometimes be necessary to manipulate meta match-patterns from CallFunc s and RemoveFunc s. The problem then is that  call-funcs  and
       remove-funcs are meta trace call-backs executed inside the inviso meta tracer's context. Hence making calls to the regular API's manipulat-
       ing meta trace-patterns will hang the inviso meta tracer!.

       To remedy this problem, a number of useful tpm-functions are available in this API. It must be understood that their actions are  local	to
       the Erlang node where they are called.

EXPORTS

       tpm_ms(Mod,Func,Arity,MSname,MS) -> {ok,0} | {ok,1} | {error,not_initiated}

	      See  inviso:tpm_ms/6  for details. Note that this function only effects meta trace-patterns on the Erlang node where the function is
	      called. This also implies that only the local inviso meta tracer's name-database is updated with MSname .

       tpm_ms_tracer(Mod,Func,Arity,MSname,MS) -> {ok,0} | {ok,1} | {error,not_initiated}

	      See inviso:tpm_ms_ms/6 for details. Note that this function only effects meta trace-patterns on the Erlang node where  the  function
	      is called. This also implies that only the local inviso meta tracer's name-database is updated with MSname .

       list_tpm_ms(Mod,Func,Arity) -> [MSname]

	      Returns  a  list	of all MSname in use for Mod:Func/Arity . This can be useful instead of having to have an own-implemented database
	      over currently in use meta match-functions for a particular function.

       ctpm_ms(Mod,Func,Arity,MSname) -> ok

	      See inviso:ctpm_ms/5 for details. Note that this function only effects meta trace-patterns on the Erlang node where the function	is
	      called. This also implies that only the local inviso meta tracer's name-database is updated with MSname .

       get_tracer() -> Tracer

	      Types  Tracer = pid() | port()

	      Returns  the  pid  or  port  acting  as the receiver of regular trace messages. This is useful if it is necessary to manipulate meta
	      trace-patterns by hand (using erlang:trace_pattern/3 ) and the {tracer,Tracer} must be used in one of the match-function bodies.

Ericsson AB							   inviso 0.6.2 					      inviso_rt_meta(3erl)