dpp(1M)dpp(1M)NAMEdpp - dedicated ports parser used by DDFA software
SYNOPSIS
dp_file log_file] ocd_program]
DESCRIPTION
The Dedicated Ports Parser command is part of the Data Communications
and Terminal Controller (DTC) Device File Access (DDFA) software. It
parses the Dedicated Ports file and spawns an Outbound Connection Dae‐
mon for each valid entry in the file.
can be run from the shell or it can be included in a system initializa‐
tion script to automatically run the DDFA software each time the system
is booted.
See ddfa(7) for more information on how to configure the DDFA software
and for an explanation of how it works.
Options and Arguments
recognizes the following options and arguments:
dp_file It must be the first argument. The file
(dp_file) defines the link between a terminal
server port and the device file used by appli‐
cations to access the port. Its contents must
meet the specifications given in dp(4). If it
is modified, must be run again to activate the
changes.
Specify that the file should be parsed and that all incorrect
entries should be logged without invoking any
processes. This option is useful for debug‐
ging the file before running it properly. The
option is ignored if the option is used.
Specify that the device file corresponding to each valid entry
in the
file should be removed before launching for
each valid entry. Removing the device file
eventually causes an process (if any is run‐
ning) to shutdown. If this option is omitted,
no device files will be removed and, there‐
fore, only newly added valid entries in the
file will have launched.
normally creates and removes devices files.
However, if the process is killed incorrectly,
such as with the device file may remain. If
the system is rebooted, the option can be
specified to restart all file entries cor‐
rectly.
If a corresponding no longer exists, the
device file is removed by any following invo‐
cation of that requires the same device file.
In order to shutdown every running without
restarting them, the following command can be
executed:
Specify where to log error messages.
If this option is omitted, all error messages
are logged to standard output.
If the specified file does not already exist,
it is created. The file must be nonexecutable
and readable by
Specify the path for an outbound connection daemon.
The default path for is The daemon must be
executable.
DIAGNOSTICS
Error messages are logged for bad arguments, bad file entries, and cre‐
ation errors. By default, they are logged to standard output. If the
option is used, they are appended to the specified log file.
The
file either does not exist or cannot be accessed
with the current access privileges.
The log file cannot be created,
either because of an invalid path or
because of insufficient access privileges.
The log file cannot be accessed,
either because of an invalid path or
because of insufficient access privileges.
The log file must be readable by everyone.
The
program specified in the option
either does not exist or is not an
executable file with the current
access privileges.
The
option has been specified and the
device file exists, but it cannot be
purged because of insufficient
access privileges.
The default
cannot be executed, either because
of insufficient access privileges or
because it has not been correctly
installed.
The
file entry specified does not have a
valid IP address.
The port specified is
either not a decimal
value
or a string composed of or
characters.
The board specified is
either not a decimal
value
or a string composed of or
characters.
The
program specified cannot be
started because there are no
processes available on the
system.
The device file
specified can‐
not be created,
either because of an
invalid path or
because of insuffi‐
cient access privi‐
leges.
The specified
configuration
file cannot be
read,
either because of an
invalid path or
because of insuffi‐
cient access privi‐
leges.
The specified
logging level
is not in the
range 0 to 3.
The specified
node name does
not exist or
does not have
an entry
in a name database.
WARNINGS
To ensure that commands (such
as ps) display the correct
device file name (that is,
the pseudonym), all pseudo‐
nyms should be placed into
the directory If pseudonyms
are not specified for place‐
ment in this directory, the
correct display of device
file names with many commands
is not guaranteed.
In addition, to ensure that
commands (such as and work
correctly, each pseudonym
must be unique in its first
17 characters (including the
directory prefix If pseudo‐
nyms are not unique in their
first 17 characters, the cor‐
rect functioning of many com‐
mands is not guaranteed.
Also, in order to reliably
handle timing mark negotia‐
tions (and ensure that files
printing on a printer
attached to a terminal server
have been completely flushed
to that printer), the follow‐
ing 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 reli‐
ability of printers attached
to a terminal server is not
guaranteed.
Finally, should be killed
using Do not use for this
purpose as it does not remove
the device file. verifies
the validity of an existing
pseudonym before trying to
use it. and use data stored
in the file to verify whether
a process still owns a pseu‐
donym before taking it over.
If finds an unowned pseudo‐
nym, it uses it.
FILESSEE ALSOocd(1M), ocdebug(1M), dp(4),
pcf(4), ddfa(7).
dpp(1M)
