Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX Reference > O


HP-UX 11i Version 3: February 2007

Technical documentation

» Feedback
Content starts here

 » Table of Contents

 » Index


ocdebug — outbound connection daemon debug utility used by DDFA software


ocdebug -fpseudonym -nnode_name [-b board_no] [-c config_file] [-d debug_level] [-l log_level] [-p port_no]


The ocdebug daemon is the debugging version of the Outbound Connection Daemon (ocd). ocd is part of the Data Communications and Terminal Controller (DTC) Device File Access (DDFA) software. It manages the connection and data transfer 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 SIGUSR1 signal to the process using:

kill -16 pid.

ocdebug logs important messages and error conditions to /var/adm/syslog. Debug messages are logged to the file /var/adm/ocdpid and the file name is displayed at the start of debugging.


ocdebug recognizes the following options. Apart from the -d option they are the same as the ocd 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 -b and -p options must not be used if the IP address given in the -n option is the IP address of a port.

If the -n option explicitly names a terminal server port, the -b 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 pcf file (/usr/examples/ddfa/pcf) 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 values):

telnet_mode: enable timing_mark: enable telnet_timer: 120 binary_mode: disable open_tries: 0 open_timer: 0 close_timer: 0 status_request: disable status_timer: 30 eight_bit: disable tcp_nodelay: enable


Specify the level of debugging. Levels can be added together to accumulate debugging functions. For example, -d7 enables all levels and -d3 enables only the first two levels. The levels 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 pty. Applications use the pseudonym and not the dynamically allocated pty slave.


Specify the logging level. It determines the severity of messages sent to /var/adm/syslog. 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 -b 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 23 (Telnet) is used by default.

In order to shutdown every ocd running without restarting them, the following command can be executed:

kill -15 `ps -e | grep ocd | awk '{print $1}'`


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 /dev/telnet. 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 w, passwd, finger, and wall) work correctly, each pseudonym must be unique in its first 17 characters (including the directory prefix /dev/telnet/). 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:

stty exta <&1 2>/dev/null

The printer interface scripts reside in the directory /etc/lp/interface. 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.


/usr/examples/ddfa/dp /usr/examples/ddfa/pcf /usr/sbin/dpp /usr/sbin/ocd /usr/sbin/ocdebug /var/adm/dpp_login.bin /var/adm/ocdpid /var/adm/syslog /var/adm/utmp.dfa

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1983-2007 Hewlett-Packard Development Company, L.P.