Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ Xconn(X) — OpenDesktop 3.0.0

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

xdaemon(X)

nameserver(X)


 Xconnections(X)               06 January 1993                Xconnections(X)


 Name

    Xconnections - format of the Xconnections file


 Description

    The ASCII file Xconnections contains the following information for each X
    server:

    1.  The name of the X server.

    2.  The protocol specific name of the host on which the X server resides.

    3.  The device name of the protocol to open for the connection.

    Fields in Xconnections are separated by white space.  Each entry is
    separated by a newline.  Lines starting with a pound sign (#) are com-
    ments.

    This file is used by AT&T SVR.2 X windows clients to determine how to
    connect to a remote server.  The first entry is the name of the X server.
    The second entry is the name of the machine on which the X server
    resides.  In general, the name of the X server and the machine will be
    the same.  Last is the name of the TLI network device in /dev that is to
    be open to establish the connection.  (Because AT&T X clients use TLI to
    establish network connections it is necessary to specify the type of net-
    work to use.)  Currently SCO only provides networked X windows support
    over the TCP/IP protocol.

    It is possible to provide a default Xconnections entry that causes any
    unresolved entry to be resolved so that the X server name is assigned to
    be the host name and the transport specified in the default entry is
    used.  This provides for ease of administration in an environment where
    there is one primary network protocol for X communications.

    To specify a default entry, set both the X server name and the host name
    to ``*''.  Because TCP/IP is the standard network protocol for X window
    connections, SCO has set the default protocol device to /dev/inet/tcp,
    the TLI device for TCP/IP communications.

    Xcommunications must be readable by all AT&T client programs for them to
    make proper requests of the xdaemon process.  However, as with
    /etc/passwd and /etc/group, this file must not be writable by users for
    security reasons.


 Example


       # This file explicitly lists the different X servers
       # that clients on this system may connect to.  It
       # also it specifies the network to use for connecting
       # to the remote system.

       atalanta        atalanta        inet/tcp
       antaeus         antaeus         inet/tcp

       # The following should always be the last entry.
       # This is the default network to use for connections
       # that are not specified above.  In this case the
       # network is TCP/IP.

       *               *               inet/tcp


 File


       /usr/X/lib/Xconnections


 See also

    xdaemon(X) and nameserver(X)


 Standards conformance

    Xconnections is conformant with:

       iBCS2 X clients


Typewritten Software • bear@typewritten.org • Edmonds, WA 98026