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)

inets(3erl)						     Erlang Module Definition						       inets(3erl)

NAME

       inets - The inets services API

DESCRIPTION

       This module provides the most basic API to the clients and servers, that are part of the Inets application, such as start and stop.

COMMON DATA TYPES

       Type definitions that are used more than once in this module:

       service() = ftpc | tftp | httpc | httpd

       property() = atom()

EXPORTS

       services() -> [{Service, Pid}]

	      Types  Service = service()
		     Pid = pid()

	      Returns a list of currently running services.

   Note:
       Services started as stand_alone will not be listed.

       services_info() -> [{Service, Pid, Info}]

	      Types  Service = service()
		     Pid = pid()
		     Info = [{Option, Value}]
		     Option = property()
		     Value = term()

	      Returns  a  list of currently running services where each service is described by a [{Option, Value}] list. The information given in
	      the list is specific for each service and it is probable that each service will have its own info function that gives you even  more
	      details about the service.

       service_names() -> [Service]

	      Types  Service = service()

	      Returns a list of available service names.

       start() ->
       start(Type) -> ok | {error, Reason}

	      Types  Type = permanent | transient | temporary

	      Starts the Inets application. Default type is temporary. See also application(3erl)

       stop() -> ok

	      Stops the inets application. See also application(3erl)

       start(Service, ServiceConfig) -> {ok, Pid} | {error, Reason}
       start(Service, ServiceConfig, How) -> {ok, Pid} | {error, Reason}

	      Types  Service = service()
		     ServiceConfig = [{Option, Value}]
		     Option = property()
		     Value = term()
		     How = inets | stand_alone - default is inets

	      Dynamically starts an inets service after the inets application has been started.

   Note:
       Dynamically  started services will not be handled by application takeover and failover behavior when inets is run as a distributed applica-
       tion. Nor will they be automatically restarted when the inets application is restarted, but as long as the inets application is up and run-
       ning  they  will  be supervised and may be soft code upgraded. Services started as stand_alone , e.i. the service is not started as part of
       the inets application, will lose all OTP application benefits such as soft upgrade. The "stand_alone-service" will be linked to the process
       that  started  it. In most cases some of the supervision functionality will still be in place and in some sense the calling process has now
       become the top supervisor.

       stop(Service, Reference) -> ok | {error, Reason}

	      Types  Service = service() | stand_alone
		     Reference = pid() | term() - service specified reference
		     Reason = term()

	      Stops a started service of the inets application or takes down a "stand_alone-service" gracefully. When the  stand_alone	option	is
	      used in start, only the pid is a valid argument to stop.

SEE ALSO

       ftp(3erl) , httpc(3erl) , httpd(3erl) , tftp(3erl)

Ericsson AB							    inets 5.5.2 						       inets(3erl)