DragonFly On-Line Manual Pages

Search: Section:  


CONFEXPORT(8)          DragonFly System Manager's Manual         CONFEXPORT(8)

NAME

confexport - configuration exporter

SYNOPSIS

confexport [-d] confexport -h

DESCRIPTION

The confexport utility is designed to be run from cron(8) to provide a dump of the confman(8) repository for use by hosts running confsync(8). If the system is already up to date, confexport will exit without making any changes. This behavior can be overridden with the -f option, which will force confexport to run even if the system revision equals the export revision. Note that the -f option cannot be used to export a revision less than the system revision. The -d option can be used to print additional debugging information. When launched with -h, confexport will display the usage statement and exit. The export generated by confexport will be written to the file specified in CONF_EXPORT_FILE (See confman.conf(5)). A persistent working copy can be specified with CONF_EXPORT_WORK_PATH in confman.conf(5). This eliminates the performance overhead of repeatedly creating and destroying temporary working copies. EXPORT STYLES The following export styles are supported by confexport: repository When using repository-style exports, confexport will generate a single tarball containing the entire confman(8) repository. The value of CONF_EXPORT_FILE in confman.conf(5) is used to specify the name of the resulting tarball. recipe When using recipe-style exports, confexport will generate a tarball for every recipe in the confman(8) repository. The value of CONF_EXPORT_FILE in confman.conf(5) is used to specify the name of the directory that will store these tarballs. module When using module-style exports, confexport will generate a tarball for each module in the confman(8) repository. The value of CONF_EXPORT_FILE in confman.conf(5) is used to specify the name of the directory that will store these tarballs.

SECURITY CONSIDERATIONS

Because a tarball with all your configurations can potentially have sensitive data, it is recommended that the System Administrator take reasonable precautions for her environment. This certainly includes consideration of the owner and group of the export file as well as the intended means for distribution of and access to the file.

SEE ALSO

confman(8), confsync(8), confman.conf(5), cron(8)

BUGS

When using confexport with the CONF_EXPORT_INCREMENTAL option, changes to files that are referenced in other modules by in-repository symlinks do not cause all relevant exports to be regenerated. This can be worked around by either disabling the CONF_EXPORT_INCREMENTAL option or running confexport with the -f flag when such changes are made.

AUTHORS

Chris Cowart <ccowart@timesinks.net> DragonFly 6.5-DEVELOPMENT May 6, 2009 DragonFly 6.5-DEVELOPMENT

Search: Section: