Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

inviso_lfm_tpfreader(3erl) [linux man page]

inviso_lfm_tpfreader(3erl)				     Erlang Module Definition					inviso_lfm_tpfreader(3erl)

NAME

       inviso_lfm_tpfreader - Inviso Standard Reader Process to Standard Logfile Merger

DESCRIPTION

       Implements the standard reader process to the standard logfile merger inviso_lfm .

       The  reader  process reads logfiles belonging to the same set (normally one node) in chronological order and delivers logged trace messages
       one by one to the output process. Before any trace messages are delivered, the inviso_lfm_tpreader implementation reads	the  entire  trace
       information file (if in use) and builds a database over pid-to-alias associations.

       The  inviso_lfm_tpreader  implementation  is capable of considering that an alias may have been used for several processes during different
       times. An alias may also be in use for several pids at the same time, on purpose. If a process has generated a trace message, all  associa-
       tions between that pid and aliases will be presented as the list PidMappings in the message sent to the output process.

EXPORTS

       handle_logfile_sort_wrapset(LogFiles) -> FileList2

	      Types  LogFiles = [{trace_log, FileList}]
		     FileList = FileList2 = [FileName]
		     FileName = string()

	      Only one {trace_log, FileList} tuple is expected in LogFiles , all other tuples are ignored. FileList must:

		* contain one single file name, or

		* a list of wraplog files, following the naming convention <Prefix><Nr><Suffix> .

	      Sorts  the  files  in  FileList  in chronological order beginning with the oldest. Sorting is only relevant if FileList is a list of
	      wraplogs. The sorting is done on finding the modulo-counter in the filename and not on filesystem timestamps.

	      This function is exported for convenience should an own reader process be implemented.

THE TRACE INFORMATION FILE PROTOCOL

       The format of a trace information file is dictated by the meta tracer process. The inviso_lfm_tpfreader implementation of a reader  process
       understands  the  following  trace  information	entries. Note that the inviso_rt_meta trace information file is on binary format prefixing
       every entry with a 4 byte length indicator.

	 {Pid, Alias, alias, NowStamp} :
	   Pid = pid()
	   Alias = term()
	   NowStamp = term() , but in current implementation as returned from erlang:now/0

	   This message indicates that from now on shall Pid be associated with Alias .

	 {MaybePid, Alias, unalias, NowStamp} :
	   MaybePid = pid() | undefined
	   Alias = term()
	   NowStamp = term() , see above

	   This message indicates that, if MaybePid is a pid, this pid shall no longer be associated with Alias . If it is undefined , all associ-
	   ations with Alias from now shall be considered invalid.

	   Also  note  that  there  are many situations where unalias entries will be missing. For instance if a process terminates without making
	   explicit function calls removing its associations first. This is seldom a problem unless the pid is reused.

Ericsson AB							   inviso 0.6.2 					inviso_lfm_tpfreader(3erl)

Check Out this Related Man Page

snmpa_network_interface(3erl)				     Erlang Module Definition				     snmpa_network_interface(3erl)

NAME

       snmpa_network_interface - Behaviour module for the SNMP agent network interface.

DESCRIPTION

       This  module  defines  the  behaviour  of the agent network interface. A snmpa_network_interface compliant module must export the following
       functions:

	 * start_link/4

	 * info/1

	 * get_log_type/1

	 * set_log_type/2

	 * verbosity/2

       The semantics of them and their exact signatures are explained below.

       But this is not enough. There is also a set of mandatory messages which the network interface entity must be able to receive and be able to
       send. This is described in chapter snmp_agent_netif .

EXPORTS

       start_link(Prio, NoteStore, MasterAgent, Opts) -> {ok, Pid} | {error, Reason}

	      Types  Prio = priority()
		     NoteStore = pid()
		     MasterAgent = pid()
		     Opts = [opt()]
		     opt() = {verbosity, verbosity()} | {versions, versions()} | term()
		     versions() = [version()]
		     version() = v1 | v2 | v3

	      Start-link the network interface process.

	      NoteStore is the pid of the note-store process and MasterAgent is the pid of the master-agent process.

	      Opts  is	an  (basically)  implementation  dependent list of options to the network interface process. There are however a number of
	      options which must be handled: versions and verbosity .

       info(Pid) -> [{Key, Value}]

	      Types  Pid = pid()

	      The info returned is basically up to the implementer to decide. This implementation provided by the application provides info  about
	      memory allocation and various socket information.

	      The  info  returned  by  this  function is returned together with other info collected by the agent when the info function is called
	      (tagged with with the key net_if ).

       verbosity(Pid, Verbosity) -> void()

	      Types  Pid = pid()
		     Verbosity = verbosity()

	      Change the verbosity of a running network interface process.

       get_log_type(Pid) -> {ok, LogType} | {error, Reason}

	      Types  Pid = pid()
		     LogType = atl_type()
		     Reason = term()

	      The Audit Trail Log is managed by the network interface process. So, it is this process that has to retrieve the actual log-type.

       set_log_type(Pid, NewType) -> {ok, OldType} | {error, Reason}

	      Types  Pid = pid()
		     NewType = OldType = atl_type()
		     Reason = term()

	      The Audit Trail Log is managed by the network interface process. So, it is this process that has to do the actual  changing  of  the
	      type.

	      See set_log_type for more info.

Ericsson AB							     snmp 4.19					     snmpa_network_interface(3erl)
Man Page