9.3 Configuring Clients with the clientSetup4SMT.sh Script

This script allows you to configure a client machine to use an SMT server. It can also be used to reconfigure an existing client to use a different SMT server.

NOTE: Installation of wget

The script clientSetup4SMT.sh itself uses wget, so wget must be installed on the client.

To configure a client machine to use SMT with the clientSetup4SMT.sh script, follow these steps:

  1. Copy the clientSetup4SMT.sh script from your SMT server to the client machine. The script is available at <SMT_HOSTNAME>/repo/tools/clientSetup4SMT.sh and /srv/www/htdocs/repo/tools/clientSetup4SMT.sh. You can download it with a browser, using wget, or by another means, such as with scp.

  2. As root, execute the script on the client machine. The script can be executed in two ways. In the first case, the script name is followed by the registration URL; for example:

    example.com./clientSetup4SMT.sh https://smt./center/regsvc/

    In the second case, the script uses the --host option followed by the hostname of the SMT server, and --regcert followed by the URL of the SSL certificate; for example:

    ./clientSetup4SMT.sh --host smt.example.com \
  --regcert http://smt.example.com/smt.crt

    In this case, without any namespace specified, the client will be configured to use the default production repositories. If --namespace groupname is specified, the client will use that staging group.

  3. The script downloads the server's CA certificate. Accept it by pressing y.

  4. The script performs all necessary modifications on the client.

  5. The script downloads and asks to accept additional GPG keys to sign repositories with.

  6. The script performs the registration by executing suse_register command on the client.

This script is also provided for download. You can get it by calling:

wget http://smt.example.com/repo/tools/clientSetup4SMT.sh

9.3.1 Problems Downloading GPG Keys from the Server

The apache2-example-pages package includes a robots.txt file. The file is installed into the Apache2 document root directory, and controls how clients can access files from the web server. If this package is installed on the server, clientSetup4SMT.sh fails to download the keys stored under /repo/keys.

You can solve this problem by either editing robots.txt, or uninstalling the apache2-example-pages package.

If you choose to edit the robots.txt file, add before the Disallow: / statement:

Allow: /repo/keys