Technical article 104763

How to perform push-down network software installations.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

Problem

I would like to know how to perform push-down software installations over the network.

Solution

This can be done using custom(ADM) (also known as the "Software Manager") from the command line.

The basic steps that need to be performed are outlined here (note that "pushes" cannot be done for the initial system load):

1. Create an "swadmin" account, giving it a password and home directory.

2. The server must have root equivalency on the client, so the server must be added to the client's root user's .rhosts file.

For example, for server "spamsco.london.sco.com" and client "sconan.london.sco.com" and entry should be placed in /.rhosts on the client ("sconan") that reads:

spamsco.london.sco.com

3. For each of the products or components that you want to "push", do one of the following on the server:

(a) Install the software  (using custom(ADM))
or
(b) Load the software (using custom(ADM))
or
(c) Place the software images in a directory

4. Push the software to the client.

When installing from installed or loaded software, as the root user on the server system, type:

# custom -h <client> -p <product> -i [<components>] \
-N <server>[:<swadmin password>]
When installing from software images, type:
# custom -h <client> -p <product> -i [<components>] \
-N <server>[:<swadmin password>] \
-z <image directory on the server>
If you don't supply the swadmin password on the command line,
custom(ADM) will prompt for it.

This is an example for pushing SCO Wabi to "sconan" from "spamsco", where the password for the "swadmin" account on "spamsco" is "swadmin_pass":

# custom -h sconan -p SCO:WABI -i -N spamsco:swadmin_pass

5. Once you have completed installing the software, you should consider removing root host equivalence between the client and the server (that is, remove /.rhosts), as this may lead to system security being compromised.

See also

custom(ADM), Chapter 17 of the SCO OpenServer Networking Guide.

From the Xinuos technical article database, record 104763. Reproduced with permission. The original is at www.sco.com/ta/104763, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.