ocdebug man page on HP-UX

Man page or keyword search:  
man Server   10987 pages
apropos Keyword Search (all sections)
Output format
HP-UX logo
[printable version]

ocdebug(1M)							   ocdebug(1M)

NAME
       ocdebug	-  outbound connection daemon debug utility used by DDFA soft‐
       ware

SYNOPSIS
       board_no] config_file] debug_level] log_level] port_no]

DESCRIPTION
       The daemon is the debugging version of the Outbound  Connection	Daemon
       is part of the Data Communications and Terminal Controller (DTC) Device
       File Access (DDFA) software.  It manages the connection and data trans‐
       fer to the remote terminal server port.

       See  ddfa(7) for more information on how to configure the DDFA software
       and for an explanation of how it works.

       Debugging may be toggled interactively by sending  the  signal  to  the
       process using:

       logs  important	messages  and  error  conditions to Debug messages are
       logged to the file and the file name  is	 displayed  at	the  start  of
       debugging.

   Options
       recognizes  the	following options.  Apart from the option they are the
       same as the options.

	      Specify the board number of a DTC.
			     If it is omitted, the  port  number  option  must
			     contain  the  full TCP service port address.  The
			     and options must not be used if  the  IP  address
			     given in the option is the IP address of a port.

			     If	 the option explicitly names a terminal server
			     port, the option is not needed.

	      Specify the name (including the absolute path)
			     of the configuration file	used  to  profile  the
			     terminal  server port.  If this value is omitted,
			     the values specified  in  the  default  file  are
			     used.   If	 the file specified does not exist, an
			     error message is logged and the following	values
			     are used (note that the values for open_tries and
			     open_timer are different from  the	 default  val‐
			     ues):

	      Specify the level of debugging.
			     Levels can be added together to accumulate debug‐
			     ging functions.  For example, enables all	levels
			     and  enables only the first two levels.  The lev‐
			     els are:

				  No debug messages.
				  Trace procedure entry/exit logged.
				  Additional tracking messages logged.
				  Data structures dumped.

	      Specify the absolute or relative path to the device file,
			     which is linked by the software to	 the  reserved
			     Applications use the pseudonym and not the dynam‐
			     ically allocated slave.

	      Specify the logging level.
			     It determines the severity of  messages  sent  to
			     The logging levels (and how they relate to system
			     logging levels) are as follows:

				  Log only LOG_CRIT messages.
				  Log only LOG_CRIT and LOG_ERR messages.
				  Log only LOG_CRIT, LOG_ERR, and  LOG_WARNING
				  messages.
				  Log all messages.

			     If it is omitted, the logging level is set to 1.

	      Specify the IP address of the terminal server or the port.

	      Specify a DTC port number or, if the
			     option  is	 omitted, the TCP port service address
			     that will be used by the software to  access  the
			     port.   If	 the value is omitted, the value (Tel‐
			     net) is used by default.

       In order to shutdown every running without restarting them, the follow‐
       ing command can be executed:

WARNINGS
       In  order  to  ensure  that  commands  (such as ps) display the correct
       device file name (that is, the pseudonym),  all	pseudonyms  should  be
       placed into the directory If pseudonyms are not specified for placement
       in this directory, the correct display of device file names  with  many
       commands is not guaranteed.

       In  addition,  in  order to ensure that commands (such as and work cor‐
       rectly, each pseudonym must  be	unique	in  its	 first	17  characters
       (including  the	directory prefix If pseudonyms are not unique in their
       first 17 characters, the correct functioning of many  commands  is  not
       guaranteed.

       Also,  in order to reliably handle timing mark negotiations (and ensure
       that files printing on a printer attached to  a	terminal  server  have
       been  completely	 flushed  to that printer), the following line must be
       added near the end  of  each  printer  interface	 script	 for  printers
       attached to a terminal server:

       The  printer interface scripts reside in the directory The line must be
       added just prior to the final 'exit' command in each printer  interface
       script.

       If  this	 line  is  not added as specified, the printing reliability of
       printers attached to a terminal server is not guaranteed.

FILES
SEE ALSO
       dpp(1M), ocd(1M), syslog(3C), dp(4), pcf(4), ddfa(7).

								   ocdebug(1M)
[top]

List of man pages available for HP-UX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net