Filter
Top Products
U23841-J-Z915-6-76 105
Configuring Xprint V7.0 Administering hosts (users only)
● Add the user xprintadm to the Xprint V7.0 configuration:
xpadd -usr xprintadm
● Modify the Xprint V7.0 configuration such that xprintadm becomes the new
Xprint V7.0 administrator:
xpmod -sys -ad xprintadm
Once you have performed these steps, you, as the Xprint V7.0 administrator,
can configure printers and other Xprint V7.0 objects on the host.
Configuring the other hosts
Configure all the other hosts as described in the following section.
6.2.3 Configuring a new host in an existing Xprint V7.0
network
Configuration hints
Xprint V7.0 allows interoperability between different administrative domains,
which need to be connected by gateways. All the hosts in an administrative
domain share the same database contents. Each definition of an Xprint V7.0
object or change of state involves a database update, which must be reflected
on each host in the domain. This database propagation mechanism requires a
reasonably fast network, which will allow connections to be opened quickly and
rapid data transfer.
The required data transfer rate between hosts is in the order of megabits per
second. A typical example of such a network is Ethernet. Different domains can
be connected by slower networks (possibly wide area networks) as there is
generally less traffic between domains than within a domain.
As a guideline, experience has shown that there is a practical limit of 50
potential masters/slave hosts in a single domain. If there are too many potential
master/slave hosts, it is difficult to keep all the databases updated. If more than
50 hosts are needed then parasite hosts can be defined, or the domain can be
divided into a number of smaller domains.
Parasite hosts import the database from their supporting host (potential master
or slave) by means of a file sharing utility (e.g. NFS) which needs to be set up
by the administrator. Parasite hosts depend on the supporting hosts, as Xprint
V7.0 cannot run on the parasite if it hasn’t been started on the supporting host.