TLP Configuration

TLP configuration is divided into three parts:

• Global configuration

• Default command-line configuration

• Module-specific configuration

For a more detailed explanation of each part, see TLP Configuration Information.

TLP Server Configuration File

TLP obtains its server configuration information from a single file. The name of the default configuration file depends on the TLP script that is running when you call the application. For example, if you call tlp, then the default configuration file that is used is conf/tlp.cfg. If you create a symbolic link, cpc, and point to tlp from this link, the default configuration file that is used is conf/cpc.cfg. With this mechanism, you can easily select different default configurations. Note that you can always override the default configuration by using the command line option, --config. For more information, see TLP Default Command-Line Options and Arguments.

TLP Client Configuration File

TLP obtains its client configuration information from a single file. The name of the default configuration file depends on the TLPC script that is running. For example. if you call tlpc, then the default configuration file that is used is conf/tlpc.cfg. If you create a symbolic link, mytlpc and point to tlpc from this link, the default configuration file that is used is conf/mytlpc.cfg. With this mechanism, you can easily select different default configurations. Note that you can always override the default configuration by using the command line option , --config.

Example 1–1 TLP Server Configuration File

This example shows the beginning portion of the TLP server configuration file. This configuration is also used as the default configuration in the conf/tlp.cfg file.

###################################################################
#
# Configuration file for TLP Patch-Management
# 
###################################################################


# ===================================================================
# Global variables 

# The global variable BaseDirectory is implictly set to the TLP
# installation directory but can be overridden. Please note, that all
# relative pathes given here are relative to the current working
# directory.
# BaseDirectory /opt/SUNWtlp

# You can define you own variables here and refer later to it, e.g if
# you define "DataDirectory  /usr/local/tlp" you can later use it like
# in "SnapshotDirectory $DataDirectory/repository"

DataDirectory $BaseDirectory/data

# Helper-Programs
# Tar /usr/bin/tar
# Uncompress /usr/bin/uncompress
# Gzip /usr/bin/gzip
# Zip /usr/bin/zip
# Bzcat /usr/bin/bzcat
# Pkginfo /usr/bin/pkginfo
# Pkgadd /usr/bin/pkgadd

...

# ===================================================================
# Patch Repository. Only one repository can be used at a time.

<Module repo>
Class Tlp::Repository::DirRepository	  # A file repository

  # Directory holding all snapshots
  SnapshotDirectory  $DataDirectory/repository
  # Directory holding phases
  PhaseDirectory     $DataDirectory/phase
  # Directory holding all Patches
  PatchDirectory     $DataDirectory/patches


  # Phases. The following directives should be given in the order
  # "most current" to "least current" (e.g. Phase "GREEN" before Phase
  # "AMBER") The interval is given in month or day differences to the
  # previous phase
	<Phase GREEN>
		Interval 30 Days
	</Phase>
	<Phase AMBER>
		Interval 3 Months
	</Phase>
</Module>

Repository repo

...

The format of the TLP server and client configuration files is similar to the well-known Apache configuration format. Lines beginning with a hash mark (#) and empty lines are ignored. Spaces at the beginning and the end of a line, as well as tabulators, are also ignored. If you need to include spaces at the end or beginning of a value, you can use double quotation marks. A configuration variable is set by giving its name, followed by an assigned value. An equal sign is optional. Path variables that contain relative paths are resolved relative to the current directory from where you called tlp.