NAME

x29uucpd − PAD UUCP server for UUCP requests to remote hosts on X.25 network

SYNOPSIS

/etc/x29uucpd [-l loglevel] [-w maxwrap] [-v]

DESCRIPTION

x29uucpd provides UUCP connectivity on X.25 networks using CCITT Recommendations X.3 and X.29.  With x29uucpd, users on HP 9000 host systems with X.25 access and UUCP can execute UUCP subsystem commands to other systems running X.25, PAD support, and UUCP.  x29uucpd interfaces with the X.25 subsystem via BSD sockets to initiate Call Request packets to remote systems on X.25.  When a Call Request arrives at a destination system, it is received by the PAD support application running on the destination system.  On HP 9000 hosts, the PAD support application is x29server.  x29uucpd interfaces with UUCP via the pty driver (see also pty(7)). The UUCP subsystem writes data to a slave device and x29uucpd reads data from the corresponding master device.  x29uucpd is thus basically a pipe through which data is passed from the pty to X.25. 

x29uucpd can be invoked at system initialization time from the /etc/netlinkrc file.  To ensure proper functionality, the X.25 subsystem should be initialized before invoking x29uucpd.  x29uucpd creates device files in /dev/x29.  The device files must be configured in the UUCP subsystem for UUCP to interface with x29uucpd. 

Options

x29uucpd recognizes the following options and command-line arguments:

-l loglevel Set the logging level for error messages from the x29uucpd daemon to logfile /usr/adm/x29/x29uucpd/x29uucpd.log.  loglevel can be one of the following values:

0 No logging. 

1 Minimum session logging and error logging. 

2 PAD and X.25 network error and warning logging plus 1. 

3 Information and status logging plus 2. 

Default is 1. 

-w maxwrap Specify maximum size for server daemon logfile.  Allowable range for maxwrap is 1 through 5000.  Default is no maxwrap.  (If the -w option is missing and loglevel is 1, 2, or 3, the daemon logfile grows indefinitely.) 

-v The -v option turns verbose on.  Verbose is off when this option is not present.  When verbose is on, explicit CAUSE of the error condition and the ACTION required for the error condition is displayed in the logfile. 

Configuration

Configuration of the UUCP destination systems for x29uucpd is provided by two files, /etc/x25/x29hosts, and /etc/x25/x3config. 

/etc/x25/x29hosts defines the configuration for x29uucpd for each UUCP destination system.  A UUCP PAD support configuration entry is identified by the keyword pad_uucp followed by information about the UUCP destination system beginning with { and ending with }.  The information required between the open and close braces specifies the device file to be used by the local UUCP subsystem, the local X.25 programmatic access name for call set-up, the X.121 address of the remote UUCP destination, the reverse charge option for X.25 calls, the logging level on a per-call basis, and the X.3 configuration set name.  An typical UUCP PAD support entry in /etc/x25/x29hosts resembles:

pad_uucp{
    device             x25uucp
    name               hptndxk0
    remote_x121        4085551113
    reverse_charge     enable
    x3                 hp_uucp
    logging            3
}

/etc/x25/x3config provides the initial X.3 parameters for the remote UUCP destinations defined in /etc/x25/x29hosts.  The example above uses hp_uucp to specify the X.3 parameter set in the /etc/x25/x3config file.  An typical hp_uucp set resembles:

hp_uucp{
     1          0
     2          0
     3          0
     4         10
     5          1
     6          0
     7          0
     8          0
     9          0
    10          0
    11         14
    12          1
    13          0
    14          0
    15          0
    16          8
    17         24
    18          0
    19          1
    20          0
    21          0
    22          0
}

The x29uucpd daemon should be invoked after the configuration for all UUCP destination systems is set up in /etc/x25/x29hosts and /etc/x25/x3config. 

Several UUCP files must be set up correctly for the interoperation of UUCP and x29uucpd.  These files reside in the /usr/lib/uucp directory.  Systems contains login information for the remote UUCP hosts.  Permissions specifies the access, send, read, write, and execute permissions for the remote UUCP hosts.  Devices contains entries for device files and other device-related information for the remote UUCP hosts.  In addition, the /usr/spool/uucp/LCK..x29 directory must exist on the local host system. 

The x29uucpd daemon forks a child for each uucp request received from UUCP (see uucp(1)). The daemon continues with waiting for requests from UUCP while the child transmits data between the local and remote systems.  When the uucp request completes, the virtual circuit is cleared, and the child process exits. 

EXTERNAL INFLUENCES

x29uucpd is implemented with native language support.  The logging can be in a foreign language by setting the environment variable LANG to correct NLS values and putting corresponding message catalog files in /usr/lib/nls.  See nlsinfo(1).

DIAGNOSTICS

x29uucpd exits if error conditions exist that cannot be corrected at start-up. 

x29uucpd: Must have root capability to start server. 
x29uucpd can be invoked only by the super-user. 

Error accessing the configuration file. 
Unrecoverable errors exist either in /etc/x25/x29hosts or in /etc/x25/x3config.  Correct the errors in the files and start x29uucpd again. 

Open error on all master devices , Open error on all slave devices
x29uucpd could not allocate pty master-slave device pairs.  Examine the state of the pty devices, correct any discrepancies between the master and slave pty devices and try again. 

x29uucpd does not exit if errors occur on specific uucp requests or X.25 connections to remote UUCP destinations.  Errors of this nature are logged to the logfiles in the directory /usr/adm/x29/x29uucpd.  The daemon logfile is x29uucpd.log.  There are also logfiles for x29uucpd children forked by the daemon.  Logfiles for the children are identified by the device name in /etc/x25/x29hosts followed by the process ID of the child.  The daemon forks a child for each X.25 connection established. 

Error messages in either the daemon or the child logfiles are timestamped and identified by a system error code, a x29uucpd error code, and a brief error message.  The format of the error message is

<date> <time> <system error code>.<x29uucpd error code> <error message>

An example of an error message is:

03/10/92 12:30:37 239.2303 Unable to connect to remote node

which says error code 239 was returned when x29uucpd tried to establish a connection to the remote UUCP system.  Error 239 in /usr/include/sys/errno.h is ECONNREFUSED which means the connection request is refused by the remote PAD support server. 

WARNINGS

If a new x29uucpd is invoked when a previous x29uucpd daemon already existed and was running on the host system, the previous x29uucpd is killed before the new x29uucpd becomes a daemon. 

x29uucpd supports 250 remote UUCP systems.  There must be one pty master-slave device pair for each remote UUCP destination configured.  The X.25 subsystem must have enough virtual circuits available to allow one virtual circuit for each remote UUCP transfer in progress. 

x29uucpd does not support permanent virtual circuits.  It can only be used on switched virtual circuits. 

x29uucpd does not support the fast-select feature in X.25. 

AUTHOR

x29uucpd was developed by HP. 

FILES

/etc/x25/x29hosts
/etc/x25/x3config

SEE ALSO

uucp(1), mail(1), uux(1), sam(1M), x25init(1M), x25stat(1), x29server(1M), x29hosts(4), x3config(4). 

UUCP HP-UX Concepts and Tutorials. 
Installing and Administering X.25/9000 ,
Troubleshooting X.25/9000 .

STANDARDS CONFORMANCE

The implementation of X.29 and X.3 protocols in x29uucpd conforms to the 1984 CCITT standards. 

Hewlett-Packard Company  —  HP-UX Release 9.10: April 1995