rdxprof - read XML LCFG profile
This command optionally fetches an XML LCFG profile from a web server and converts it into a DBM file. If no hostname is specified, the profile for the local host is used.
rdxprof is normally run from the LCFG client component.
/usr/sbin/rdxprof [options] [hostname]
If this option is present, rdxprof will send UDP acknowledgements on service port lcfgack (default 733) to the server(s) containing the timestamp of the last received profile.
When running as a daemon and sending server acknowledgements, this option specifies the minimum and maximum times between acknowledgements in the form minh|m|s[+maxh|m|s]. Acknowledgements will never be sent faster than min apart, and will never be delayed for more than max.
Error messages are passed to the log system for the named component.
If this option is present, rdxprof runs as a daemon, polling or waiting for notifications of changed profiles.
This option enables debugging for the categories listed by the comma-separated list of flags. Possible flags are ack, all, attrs, callbacks, context, changes, daemon, fetch, parse, rpms. Flags may be prefixed with + or - to enable/disable specific categories.
If this option is specified, then rdxprof will notify other components when their resources change by calling the method specified in the client.reconfig_component resource.
When running as a daemon, this option species an interval to poll for new profiles. It has the format: timeh|m|s[+randomh|m|s]. The random addition can be used to distribute server load.
A prefix to be used for all pathnames. This is used by the profile component at install time when the root of the client filesystem is not the same as the current root.
This option specifies the the client component is running and should be be reconfigured if its resources change.
Enable secure mode. Profile changes will require manual validation.
The timeout interval for HTTP requests, in the form timeh|m|s.
A comma-separated list of URLs for servers containing copies of the profile. If the URLs do not end in .xml, rdxprof will append domain/hostname/XML/profile.xml. rdxprof will then attempt to fetch new profiles from the specified URLs in random order. If this option is not present, the profile is assumed to already exist in /var/lcfg/conf/profile/xml. If any file: URLs are specified, they are tried before remote URLs. URLs staring with none: are ignored (this may be useful for passing to the client install method). A URL consisting simply of the string file: is assumed to refere to the default location of the local profile (this is useful during the install process).
If this option is present, the component method component method will be called whenever any RPMs in the profile change. The method may be followed by any necessary options. This requires the -n option.
Verbose.
This option enables warnings for the categories listed by the comma-separated list of flags. Possible flags are all, conflict, context, notify, error, fetch, parse, rpms, server. Flags may be prefixed with + or - to enable/disable specific categories.
The the path of the directory containing the profile file (with the name profile.xml). If a client and server are both running on the same machine, it is useful to set this to the pathname of the profile directory used by the server. This allows the client to retrieve new profiles directly from the local disk, as they are generated by the server, without requiring a running web server.
When not running in daemon mode, rdxprof will attempt to fetch the profile from the specified URL (if any) and rebuild the dbm file.
When running in daemon mode, a new profile will only be fetched if it is newer than the current profile. This will only be rebuilt into a new dbm file, if the profile is newer than the dbm file.
In daemon mode, UDP packets on service port lcfg (default 732) can be sent by mkxprof to initiate a poll for new profile. The following signals are also recognised:
This is equivalent to a notification packet from the server; it initiates a poll for a new profile.
This initiates a rebuild of the dbm file, if the profile, or the context has changed. This signal is sent by the client component after changing the context.
The initiates a rebuild of the dbm file regardless of any changes to the profile or the context.
This requests an acknowledgement to be sent to the server.
Requests server termination.
The directory containing the profiles.
The directory containing the generated DBM files.
The directory containing the context files.
The directory containing the client RPM configuration files.
Solaris9, Fedora3, Darwin, Fedora5, Fedora6, Scientific5
Paul Anderson <dcspaul@inf.ed.ac.uk>