profile - client resources used by the LCFG server
There is no LCFG profile component, but profile resources for an LCFG client are used by mkxprof when compiling a client profile. Every client whose profile is to be generated by mkxprof (lcfg-server) must have a set of profile resources.
An Apache "allow from" specification for the access file corresponding to access_file, specifying hosts which should be permitted to access this profile without authentication.
A list of tags representing Apache web access files to be created in the profile directory for this host.
The name of a Perl module to use for default authorization (for example by om). This is not used by the client, or the server; it simply provides a common source of reference for other components. The default is LCFG::Authorize.
A comment for inclusion on the server status page.
A space-separated list of components whose resources are to be included in the profile. mkxprof wil not generate profiles for components not specified in this resource.
The client domain. This defaults to the same domain as the server.
The name of the Apache access file for the given access_file. Normally, this will be .htaccess, but Apache may be configured to use multiple different access files in different circumstances: for example, a different access file may be used for SSL and plain HTTP.
This resource specifies the name of the Perl module used to generate the profile. This can be used to generate profiles in different formats. The only format currently supported (and the default) is XML.
It is sometime useful to have entries which are not intended to generate live profiles; for example, an entry may be included for inventory purposes, or for its contribution to a spanning map. In this case, the profile format can be declared as type stub. If this is followed by a URL, the icons in the status display will be linked to the given URL - this is useful for servers which have stub entries for live profiles which reside on other servers.
An (optional) three digit numeric order number, followed by a title string. Hosts are grouped by group in the server status display. The title string is the title for the display section and the order number is used to sort the sections. By default, the group is set to the domain, and the order number is 100.
The maximum time expected between package updates on the client. A warning icon will be displayed on the status page, if the client has not performed a successful package update within the last maxupdate. The value of the resource should be an integer, followed by h (hours).
The client node name (host name). This is the name of the source file. This value will be substituted for the string %h in the pathnames of any directories included by the server. If this is null, the string default will be substituted.
Any header or package list path containing a %h
If this resource is true, a UDP notification wil be sent to the node whenever the profile changes.
A list of package specifications (eg. RPMs) to be included in the profile. Each specification may be either:
The specification is the name of the file, proceeded by @. The file should contain a list of package names of the form name-version-release{:options}, optionally proceeded by + or -.
Of the form name-version-release{:options}, optionally proceeded by + or -.
This is tag for a resource name of the form profile.packages_tag which is assumed to contain further package specifications (these can be nested to an arbitrary depth).
Package specifications occuring either in a resource value, or in a file may be followed by a context specifier in the usual form. Context specifications are not permitted on the tagged resources, or on filenames.
The passwd for web access. This is entered into the password database which is referenced by the access control file to protect the directory containing the profile. This resource is cached separately by the client so that it is only available to root processes. The value is returned as "****" by the client libraries if it set, and null otherwise.
Additional options to be passed to cpp when reading package list files.
The name of an Apache DB password file which will be used to to authenticate profile requests when the access control conditions are not satisified (see acl_access_file), or not present. The client will attempt connections using the FQDN of the host as the username, and the value of the profile.passwd resource as the password. The special value auto can be supplied in which case the server will use the password file created automatically from the profile.passwd resources.
The configuration release. This value will be substituted for the string %r in the pathnames of any directories included by the server. If this is null, the string default will be substituted.
The groupname under which the LCFG system runs by default on the client.
The username under which the LCFG system runs by default on the client.
The expected software release version on the client. If this resource is present, then a warning icon will be displayed unless the release string matches the contents of /etc/LCFG-RELEASE.
This resource specifies the version of the .def file to be used for the specified component. The file is named component-version.def or component.def (if there is no version specified).
Paul Anderson <dcspaul@inf.ed.ac.uk>