machinery-tool 1.18.0 → 1.19.0

data/manual/docs/machinery-show.1.md

@@ -3,7 +3,7 @@
 
 ## SYNOPSIS
 
-`machinery show` [-s SCOPE | --scope=SCOPE] [-e EXCLUDE-SCOPE | --exclude-scope=EXCLUDE-SCOPE] [--no-pager] [--show-diffs] [--html] NAME
+`machinery show` [-s SCOPE | --scope=SCOPE] [-e IGNORE-SCOPE | --ignore-scope=IGNORE-SCOPE] [--no-pager] [--show-diffs] [--html] NAME
 
 `machinery` help show
 
@@ -30,7 +30,7 @@ in local time are shown in the title of each scope section.
     If displaying information related to a scope fails, `show` will print an error message what has failed.
     In case of an error, no content is displayed.
 
-  * `-e EXCLUDE-SCOPE`, `--exclude-scope=EXCLUDE-SCOPE` (optional):
+  * `-e IGNORE-SCOPE`, `--ignore-scope=IGNORE-SCOPE` (optional):
     Skip output of the specified scope.
     See the [Scope section](#Scopes) for more information.
 

data/manual/docs/machinery_main_general.1.md

@@ -105,7 +105,7 @@ name which can be used by all subcommands.
 
 The system description is structured into "scopes". A scope covers a specific
 part of the configuration of the inspected system such as installed packages,
-repositories, or configuration files.
+repositories, or changed configuration files.
 
 For example, if you are only interested in the installed packages, limit the
 scope to `packages`. This will output only the requested information.

data/manual/docs/machinery_main_scopes.1.md

@@ -10,11 +10,13 @@ inspected system.
 
 * patterns
 
-Contains all patterns installed on the inspected system. A pattern is a
-collection of software packages.
+Contains all patterns or tasks installed on the inspected system. A pattern is a
+collection of software packages, similar to the idea of tasks on Debian/Ubuntu-
+like systems.
 The meaning of software patterns depends on the package manager of the
 distribution. Therefore, the pattern scope on SUSE based systems uses the
-`zypper` command to obtain the information about installed pattern names.
+`zypper` command to obtain the information about installed pattern names, whereas
+on Debian based systems the `tasksel` tool is necessary to list installed tasks.
 
 * repositories
 
@@ -61,13 +63,13 @@ or waiting for requests to do work.
 The scope determines which services are configured to be started in which
 runlevel. It uses the `chkconfig` command to obtain that information.
 The xinetd services that are also displayed by `chkconfig` are switched
-on/off by editing config files and are ignored in this context.
+on/off by editing configuration files and are ignored in this context.
 
-* config_files
+* changed_config_files
 
 Contains all configuration files which have been changed since they were
 installed.
-Configuration files are all those files which are marked as such in the
+Changed configuration files are all those files which are marked as such in the
 package which has installed them. A configuration file change is reported
 if its content or its attributes like Linux permission bits or ownership
 have changed.

data/manual/site/machinery-analyze.1/index.html

@@ -139,8 +139,8 @@
 <p>The <code>analyze</code> subcommand analyzes an existing system description and enriches
 it with additional information. Supported operations are:</p>
 <ul>
-<li><code>config-file-diffs</code>:
-    Generates the diffs between the extracted changed config files from the
+<li><code>changed-config-files-diffs</code>:
+    Generates the diffs between the extracted changed configuration files from the
     system and the original versions from the RPM packages.
     The diffs can be shown using <code>machinery show --show-diffs</code></li>
 </ul>
@@ -158,7 +158,7 @@ it with additional information. Supported operations are:</p>
 <ul>
 <li>
 <p>Analyze the config file diffs for the <code>myhost</code> system description:</p>
-<p>$ <code>machinery</code> analyze myhost --operation=config-file-diffs</p>
+<p>$ <code>machinery</code> analyze myhost --operation=changed-config-files-diffs</p>
 </li>
 </ul>
       </div>

data/manual/site/machinery-compare.1/index.html

@@ -133,7 +133,7 @@
       <div class="content">
         <h1 id="compare-compare-system-descriptions">compare — Compare System Descriptions</h1>
 <h2 id="synopsis">SYNOPSIS</h2>
-<p><code>machinery compare</code> [-s SCOPE | --scope=SCOPE] [-e EXCLUDE-SCOPE | --exclude-scope=EXCLUDE-SCOPE] [--no-pager] [--show-all] [--html] NAME1 NAME2</p>
+<p><code>machinery compare</code> [-s SCOPE | --scope=SCOPE] [-e IGNORE-SCOPE | --ignore-scope=IGNORE-SCOPE] [--no-pager] [--show-all] [--html] NAME1 NAME2</p>
 <p><code>machinery</code> help compare</p>
 <h2 id="description">DESCRIPTION</h2>
 <p>The <code>compare</code> command compares stored system descriptions. The scope option can
@@ -157,7 +157,7 @@ be used to limit the output to the given scopes.</p>
     See the <a href="#Scopes">Scope section</a> for more information.</p>
 </li>
 <li>
-<p><code>-e SCOPE</code>, <code>--exclude-scope=EXCLUDE-SCOPE</code> (optional):
+<p><code>-e SCOPE</code>, <code>--ignore-scope=IGNORE-SCOPE</code> (optional):
     Skip output of the specified scope.
     See the <a href="#Scopes">Scope section</a> for more information.</p>
 </li>

data/manual/site/machinery-inspect-docker.1/index.html

@@ -165,7 +165,7 @@ trigger errors.</p>
     See the <a href="#Scopes">Scope section</a> for more information.</p>
 </li>
 <li>
-<p><code>-e SCOPE</code>, <code>--exclude-scope=EXCLUDE-SCOPE</code> (optional):
+<p><code>-e SCOPE</code>, <code>--ignore-scope=IGNORE-SCOPE</code> (optional):
     Inspect image for all scopes except the specified scope.
     See the <a href="#Scopes">Scope section</a> for more information.</p>
 </li>

data/manual/site/machinery-inspect.1/index.html

@@ -143,6 +143,8 @@ description from the gathered data.</p>
 <p><strong>Note</strong>:
 Machinery will always inspect all specified scopes, and skip scopes which
 trigger errors.</p>
+<p><strong>Note</strong>:
+Tasks on Debian-like systems are treated as patterns.</p>
 <h2 id="arguments">ARGUMENTS</h2>
 <ul>
 <li><code>HOSTNAME</code> (required):
@@ -162,7 +164,7 @@ trigger errors.</p>
     See the <a href="../machinery_main_scopes.1/index.html">Scope section</a> for more information.</p>
 </li>
 <li>
-<p><code>-e SCOPE</code>, <code>--exclude-scope=EXCLUDE-SCOPE</code> (optional):
+<p><code>-e SCOPE</code>, <code>--ignore-scope=IGNORE-SCOPE</code> (optional):
     Inspect system for all scopes except the specified scope.
     See the <a href="../machinery_main_scopes.1/index.html">Scope section</a> for more information.</p>
 </li>

data/manual/site/machinery-show.1/index.html

@@ -133,7 +133,7 @@
       <div class="content">
         <h1 id="show-show-system-description">show — Show System Description</h1>
 <h2 id="synopsis">SYNOPSIS</h2>
-<p><code>machinery show</code> [-s SCOPE | --scope=SCOPE] [-e EXCLUDE-SCOPE | --exclude-scope=EXCLUDE-SCOPE] [--no-pager] [--show-diffs] [--html] NAME</p>
+<p><code>machinery show</code> [-s SCOPE | --scope=SCOPE] [-e IGNORE-SCOPE | --ignore-scope=IGNORE-SCOPE] [--no-pager] [--show-diffs] [--html] NAME</p>
 <p><code>machinery</code> help show</p>
 <h2 id="description">DESCRIPTION</h2>
 <p>The <code>show</code> command displays a stored system description.
@@ -155,7 +155,7 @@ in local time are shown in the title of each scope section.</p>
     In case of an error, no content is displayed.</p>
 </li>
 <li>
-<p><code>-e EXCLUDE-SCOPE</code>, <code>--exclude-scope=EXCLUDE-SCOPE</code> (optional):
+<p><code>-e IGNORE-SCOPE</code>, <code>--ignore-scope=IGNORE-SCOPE</code> (optional):
     Skip output of the specified scope.
     See the <a href="#Scopes">Scope section</a> for more information.</p>
 </li>

data/manual/site/machinery_main_general.1/index.html

@@ -226,7 +226,7 @@ name which can be used by all subcommands.</p>
 <h2 id="scopes">Scopes</h2>
 <p>The system description is structured into "scopes". A scope covers a specific
 part of the configuration of the inspected system such as installed packages,
-repositories, or configuration files.</p>
+repositories, or changed configuration files.</p>
 <p>For example, if you are only interested in the installed packages, limit the
 scope to <code>packages</code>. This will output only the requested information.</p>
 <p>The the <a href="../machinery_main_scopes.1">scopes documentation</a> for a list of all supported scopes.</p>

data/manual/site/machinery_main_scopes.1/index.html

@@ -144,11 +144,13 @@ inspected system.</p>
 <ul>
 <li>patterns</li>
 </ul>
-<p>Contains all patterns installed on the inspected system. A pattern is a
-collection of software packages.
+<p>Contains all patterns or tasks installed on the inspected system. A pattern is a
+collection of software packages, similar to the idea of tasks on Debian/Ubuntu-
+like systems.
 The meaning of software patterns depends on the package manager of the
 distribution. Therefore, the pattern scope on SUSE based systems uses the
-<code>zypper</code> command to obtain the information about installed pattern names.</p>
+<code>zypper</code> command to obtain the information about installed pattern names, whereas
+on Debian based systems the <code>tasksel</code> tool is necessary to list installed tasks.</p>
 <ul>
 <li>repositories</li>
 </ul>
@@ -204,13 +206,13 @@ or waiting for requests to do work.
 The scope determines which services are configured to be started in which
 runlevel. It uses the <code>chkconfig</code> command to obtain that information.
 The xinetd services that are also displayed by <code>chkconfig</code> are switched
-on/off by editing config files and are ignored in this context.</p>
+on/off by editing configuration files and are ignored in this context.</p>
 <ul>
-<li>config_files</li>
+<li>changed_config_files</li>
 </ul>
 <p>Contains all configuration files which have been changed since they were
 installed.
-Configuration files are all those files which are marked as such in the
+Changed configuration files are all those files which are marked as such in the
 package which has installed them. A configuration file change is reported
 if its content or its attributes like Linux permission bits or ownership
 have changed.</p>

data/manual/site/mkdocs/search_index.json

@@ -12,7 +12,7 @@
         },
         {
             "location": "/machinery_main_general.1/",
-            "text": "Machinery \u2014 A Systems Management Toolkit for Linux\n\n\nSYNOPSIS\n\n\nmachinery\n SUBCOMMAND [options] \n\n\nmachinery\n help [SUBCOMMAND]\n\n\nDESCRIPTION\n\n\nMachinery is a systems management toolkit for Linux. It supports configuration\ndiscovery, system validation, and service migration. Machinery is based on the\nidea of an universal system description. Machinery has a set of commands which\nwork with this system description. These commands can be combined to form work\nflows. Machinery is targeted at the system administrator of the data center.\n\n\nWORK FLOW EXAMPLES\n\n\nInspect a System and Show Results\n\n\n\n\nmachinery inspect --extract-files --name=NAME HOSTNAME\n\n\nmachinery show NAME\n\n\n\n\nInspect Two Systems and Compare Them\n\n\n\n\nmachinery inspect HOSTNAME1\n\n\nmachinery inspect HOSTNAME2\n\n\nmachinery compare HOSTNAME1 HOSTNAME2\n\n\n\n\nFully Inspect a System and Export a Kiwi Description\n\n\n\n\nmachinery inspect --extract-files HOSTNAME\n\n\nmachinery export-kiwi --kiwi-dir=~/kiwi HOSTNAME\n\n\n\n\nFully Inspect a System and Export an AutoYaST Profile\n\n\n\n\nmachinery inspect --extract-files HOSTNAME\n\n\nmachinery export-autoyast --autoyast-dir=~/autoyast HOSTNAME\n\n\n\n\nFully Inspect a System and Deploy a Replicate to the Cloud\n\n\n\n\nmachinery inspect --extract-files HOSTNAME\n\n\nmachinery deploy --cloud-config=~/openrc.sh HOSTNAME\n\n\n\n\nHow to upgrade a SLES 11 SP3 system to SLES 12\n\n\n\n\nMachinery can help you to upgrade without affecting the original system.\n    For more details please read the Wiki Page: \n\n    https://github.com/SUSE/machinery/wiki/How-to-upgrade-a-SLES-11-SP3-system-to-SLES-12\n\n\n\n\nCONCEPTUAL OVERVIEW\n\n\nMachinery's core concept is the complete representation of a system by a\nuniversal system description.\nSystem descriptions are managed independently of the described\nsystems which allows for system state conservation and offline preparation of\nmodifications.\n\n\nMachinery's subcommands work on the system description as the connecting\nelement.\nSystem descriptions are obtained by inspecting systems, importing from other\nformats, manual creation or merging other descriptions.\nMachinery can store and modify system descriptions to allow changes to\ndescribed state of the system.\nSystem descriptions can be compared to find similarities and differences\nbetween them or analyzed to deepen the knowledge about particular aspects of\nthe system.\nSystem descriptions may be exported to other formats and can be used to\nmigrate or replicate systems.\n\n\nSubcommands can be combined in different ways to accomodate higher-level work\nflows and use cases.\nThese are some implemented and planned use cases:\n\n\nMigrate a physical system to a virtual environment:\n\n\n\n\nInspect a system to obtain a system description\n\n\nExport the system description to a Kiwi configuration\n\n\nBuild a cloud image from the configuration\n\n\nDeploy the image to the cloud\n\n\n\n\nMigrate a system while changing the configuration:\n\n\n\n\nInspect a system to obtain a system description\n\n\nModify the system description\n\n\nBuild image for deployment\n\n\n\n\nUsing Machinery as an extension from other formats:\n\n\n\n\nImport AutoYaST profile as system description\n\n\nBuild image for deployment\n\n\n\n\nMachinery provides an extensible set of tools which can be combined to create\nhigher-level work flows.\nIt is designed for environments which focus on automation, integration\nof diverse tools and accountable management.\nMachinery integrates with existing configuration management solutions to\naddress use cases currently not covered by them.\n\n\nThe machinery Command\n\n\nMachinery is implemented as a command line tool named \nmachinery\n. The\n\nmachinery\n command has several subcommands for specific tasks. All\nsubcommands work with the same system description identified by an optional\nname which can be used by all subcommands.\n\n\nScopes\n\n\nThe system description is structured into \"scopes\". A scope covers a specific\npart of the configuration of the inspected system such as installed packages,\nrepositories, or configuration files.\n\n\nFor example, if you are only interested in the installed packages, limit the\nscope to \npackages\n. This will output only the requested information.\n\n\nThe the \nscopes documentation\n for a list of all supported scopes.\n\n\nFILES AND DEVICES\n\n\n\n\n\n\n~/.machinery/machinery.config\n:\n\n\nConfiguration file.\n\n\n\n\n\n\n~/.machinery/machinery.log\n:\n\n\nCentral log file, in the format date, time, process id, and log message.\n\n\n\n\n\n\neth0\n (SLE11) and \nlan0\n (SLE12):\n\n\nFirst network device is used when DHCP in built image is enabled.\n\n\n\n\n\n\nENVIRONMENT\n\n\n\n\n\n\nMACHINERY_LOG_FILE\n:\n\n\nLocation of Machinery's log file (defaults to \n~/.machinery/machinery.log\n)\n\n\n\n\n\n\nCOPYRIGHT\n\n\nCopyright (c) 2013-2016 \nSUSE LLC",
+            "text": "Machinery \u2014 A Systems Management Toolkit for Linux\n\n\nSYNOPSIS\n\n\nmachinery\n SUBCOMMAND [options] \n\n\nmachinery\n help [SUBCOMMAND]\n\n\nDESCRIPTION\n\n\nMachinery is a systems management toolkit for Linux. It supports configuration\ndiscovery, system validation, and service migration. Machinery is based on the\nidea of an universal system description. Machinery has a set of commands which\nwork with this system description. These commands can be combined to form work\nflows. Machinery is targeted at the system administrator of the data center.\n\n\nWORK FLOW EXAMPLES\n\n\nInspect a System and Show Results\n\n\n\n\nmachinery inspect --extract-files --name=NAME HOSTNAME\n\n\nmachinery show NAME\n\n\n\n\nInspect Two Systems and Compare Them\n\n\n\n\nmachinery inspect HOSTNAME1\n\n\nmachinery inspect HOSTNAME2\n\n\nmachinery compare HOSTNAME1 HOSTNAME2\n\n\n\n\nFully Inspect a System and Export a Kiwi Description\n\n\n\n\nmachinery inspect --extract-files HOSTNAME\n\n\nmachinery export-kiwi --kiwi-dir=~/kiwi HOSTNAME\n\n\n\n\nFully Inspect a System and Export an AutoYaST Profile\n\n\n\n\nmachinery inspect --extract-files HOSTNAME\n\n\nmachinery export-autoyast --autoyast-dir=~/autoyast HOSTNAME\n\n\n\n\nFully Inspect a System and Deploy a Replicate to the Cloud\n\n\n\n\nmachinery inspect --extract-files HOSTNAME\n\n\nmachinery deploy --cloud-config=~/openrc.sh HOSTNAME\n\n\n\n\nHow to upgrade a SLES 11 SP3 system to SLES 12\n\n\n\n\nMachinery can help you to upgrade without affecting the original system.\n    For more details please read the Wiki Page: \n\n    https://github.com/SUSE/machinery/wiki/How-to-upgrade-a-SLES-11-SP3-system-to-SLES-12\n\n\n\n\nCONCEPTUAL OVERVIEW\n\n\nMachinery's core concept is the complete representation of a system by a\nuniversal system description.\nSystem descriptions are managed independently of the described\nsystems which allows for system state conservation and offline preparation of\nmodifications.\n\n\nMachinery's subcommands work on the system description as the connecting\nelement.\nSystem descriptions are obtained by inspecting systems, importing from other\nformats, manual creation or merging other descriptions.\nMachinery can store and modify system descriptions to allow changes to\ndescribed state of the system.\nSystem descriptions can be compared to find similarities and differences\nbetween them or analyzed to deepen the knowledge about particular aspects of\nthe system.\nSystem descriptions may be exported to other formats and can be used to\nmigrate or replicate systems.\n\n\nSubcommands can be combined in different ways to accomodate higher-level work\nflows and use cases.\nThese are some implemented and planned use cases:\n\n\nMigrate a physical system to a virtual environment:\n\n\n\n\nInspect a system to obtain a system description\n\n\nExport the system description to a Kiwi configuration\n\n\nBuild a cloud image from the configuration\n\n\nDeploy the image to the cloud\n\n\n\n\nMigrate a system while changing the configuration:\n\n\n\n\nInspect a system to obtain a system description\n\n\nModify the system description\n\n\nBuild image for deployment\n\n\n\n\nUsing Machinery as an extension from other formats:\n\n\n\n\nImport AutoYaST profile as system description\n\n\nBuild image for deployment\n\n\n\n\nMachinery provides an extensible set of tools which can be combined to create\nhigher-level work flows.\nIt is designed for environments which focus on automation, integration\nof diverse tools and accountable management.\nMachinery integrates with existing configuration management solutions to\naddress use cases currently not covered by them.\n\n\nThe machinery Command\n\n\nMachinery is implemented as a command line tool named \nmachinery\n. The\n\nmachinery\n command has several subcommands for specific tasks. All\nsubcommands work with the same system description identified by an optional\nname which can be used by all subcommands.\n\n\nScopes\n\n\nThe system description is structured into \"scopes\". A scope covers a specific\npart of the configuration of the inspected system such as installed packages,\nrepositories, or changed configuration files.\n\n\nFor example, if you are only interested in the installed packages, limit the\nscope to \npackages\n. This will output only the requested information.\n\n\nThe the \nscopes documentation\n for a list of all supported scopes.\n\n\nFILES AND DEVICES\n\n\n\n\n\n\n~/.machinery/machinery.config\n:\n\n\nConfiguration file.\n\n\n\n\n\n\n~/.machinery/machinery.log\n:\n\n\nCentral log file, in the format date, time, process id, and log message.\n\n\n\n\n\n\neth0\n (SLE11) and \nlan0\n (SLE12):\n\n\nFirst network device is used when DHCP in built image is enabled.\n\n\n\n\n\n\nENVIRONMENT\n\n\n\n\n\n\nMACHINERY_LOG_FILE\n:\n\n\nLocation of Machinery's log file (defaults to \n~/.machinery/machinery.log\n)\n\n\n\n\n\n\nCOPYRIGHT\n\n\nCopyright (c) 2013-2016 \nSUSE LLC",
             "title": "General"
         },
         {
@@ -77,7 +77,7 @@
         },
         {
             "location": "/machinery_main_general.1/#scopes",
-            "text": "The system description is structured into \"scopes\". A scope covers a specific\npart of the configuration of the inspected system such as installed packages,\nrepositories, or configuration files.  For example, if you are only interested in the installed packages, limit the\nscope to  packages . This will output only the requested information.  The the  scopes documentation  for a list of all supported scopes.",
+            "text": "The system description is structured into \"scopes\". A scope covers a specific\npart of the configuration of the inspected system such as installed packages,\nrepositories, or changed configuration files.  For example, if you are only interested in the installed packages, limit the\nscope to  packages . This will output only the requested information.  The the  scopes documentation  for a list of all supported scopes.",
             "title": "Scopes"
         },
         {
@@ -97,7 +97,7 @@
         },
         {
             "location": "/machinery_main_scopes.1/",
-            "text": "os\n\n\n\n\nContains information about the operating system, name, version, and\narchitecture of the inspected system.\n\n\n\n\npackages\n\n\n\n\nContains information on all installed RPM packages installed on the\ninspected system.\n\n\n\n\npatterns\n\n\n\n\nContains all patterns installed on the inspected system. A pattern is a\ncollection of software packages.\nThe meaning of software patterns depends on the package manager of the\ndistribution. Therefore, the pattern scope on SUSE based systems uses the\n\nzypper\n command to obtain the information about installed pattern names.\n\n\n\n\nrepositories\n\n\n\n\nContains all information about software repositories configured on the\ninspected system. The information about repositories depends on the package\nmanager of the distribution. Thus on SUSE-based systems the \nzypper\n command\nis used. Machinery collects the following information from each configured repository:\n\n\n\n\n\n\nThe alias name of the repository.\n\n\n\n\n\n\nThe repository type, rpm-md and YaST types that are used on SUSE systems.\n\n\n\n\n\n\nThe path to the repository. This could be a local path, a remote location,\n  a device, or a file.\n\n\n\n\n\n\nA boolean flag that indicates if this repository is in use or not.\n\n\n\n\n\n\nA boolean flag that indicates if this repository should update the locally\n  stored metadata files with metadata files from the origin automatically or\n  not.\n\n\n\n\n\n\nA boolean flag that indicates if packages which would be installed from\n  this repository should be checked by their gpg key or not.\n\n\n\n\n\n\nA numeric value for a priority. The priority of a repository is compared\n  to the priorities of all other activated repositories. Values can\n  range from 1 (highest) to 99 (lowest, default).\n\n\n\n\n\n\nusers\n\n\n\n\n\n\nContains information about the system users including user and group ids,\nlogin information, such as password hashes and - if available - additional\npassword properties.\n\n\n\n\ngroups\n\n\n\n\nContains information about the system groups such as group attributes and the\nlist of group members.\n\n\n\n\nservices\n\n\n\n\nServices are applications running in the background doing continuous work\nor waiting for requests to do work.\nThe scope determines which services are configured to be started in which\nrunlevel. It uses the \nchkconfig\n command to obtain that information.\nThe xinetd services that are also displayed by \nchkconfig\n are switched\non/off by editing config files and are ignored in this context.\n\n\n\n\nconfig_files\n\n\n\n\nContains all configuration files which have been changed since they were\ninstalled.\nConfiguration files are all those files which are marked as such in the\npackage which has installed them. A configuration file change is reported\nif its content or its attributes like Linux permission bits or ownership\nhave changed.\n\n\n\n\nchanged_managed_files\n\n\n\n\nContains the names and contents of all non-configuration files which have\nbeen changed compared to the files in the package. A file change is reported\nif its content or its attributes like Linux permission bits or ownership\nhave changed.\n\n\n\n\nunmanaged_files\n\n\n\n\nContains the names and contents of all files which are not part of any RPM\npackage. The list of unmanaged files contains only plain files and\ndirectories. Special files like device nodes, named pipes and Unix domain\nsockets are ignored. The directories \n/tmp\n,  \n/var/tmp\n, \n/.snapshots/\n,\n\n/var/run\n and special mounts like procfs and sysfs are ignored, too.\nIf a directory is in this list, no file or directory below it belongs to a\nRPM package.\n\n\nMeta data information of unmanaged files is only available if the files were\nextracted during inspection.\n\n\nUsing the \n--extract-unmanaged-files\n option, the files are transferred from\nthe system and stored in the system description. Depending on the content of\nthe inspected system, the amount of data stored may be huge.",
+            "text": "os\n\n\n\n\nContains information about the operating system, name, version, and\narchitecture of the inspected system.\n\n\n\n\npackages\n\n\n\n\nContains information on all installed RPM packages installed on the\ninspected system.\n\n\n\n\npatterns\n\n\n\n\nContains all patterns or tasks installed on the inspected system. A pattern is a\ncollection of software packages, similar to the idea of tasks on Debian/Ubuntu-\nlike systems.\nThe meaning of software patterns depends on the package manager of the\ndistribution. Therefore, the pattern scope on SUSE based systems uses the\n\nzypper\n command to obtain the information about installed pattern names, whereas\non Debian based systems the \ntasksel\n tool is necessary to list installed tasks.\n\n\n\n\nrepositories\n\n\n\n\nContains all information about software repositories configured on the\ninspected system. The information about repositories depends on the package\nmanager of the distribution. Thus on SUSE-based systems the \nzypper\n command\nis used. Machinery collects the following information from each configured repository:\n\n\n\n\n\n\nThe alias name of the repository.\n\n\n\n\n\n\nThe repository type, rpm-md and YaST types that are used on SUSE systems.\n\n\n\n\n\n\nThe path to the repository. This could be a local path, a remote location,\n  a device, or a file.\n\n\n\n\n\n\nA boolean flag that indicates if this repository is in use or not.\n\n\n\n\n\n\nA boolean flag that indicates if this repository should update the locally\n  stored metadata files with metadata files from the origin automatically or\n  not.\n\n\n\n\n\n\nA boolean flag that indicates if packages which would be installed from\n  this repository should be checked by their gpg key or not.\n\n\n\n\n\n\nA numeric value for a priority. The priority of a repository is compared\n  to the priorities of all other activated repositories. Values can\n  range from 1 (highest) to 99 (lowest, default).\n\n\n\n\n\n\nusers\n\n\n\n\n\n\nContains information about the system users including user and group ids,\nlogin information, such as password hashes and - if available - additional\npassword properties.\n\n\n\n\ngroups\n\n\n\n\nContains information about the system groups such as group attributes and the\nlist of group members.\n\n\n\n\nservices\n\n\n\n\nServices are applications running in the background doing continuous work\nor waiting for requests to do work.\nThe scope determines which services are configured to be started in which\nrunlevel. It uses the \nchkconfig\n command to obtain that information.\nThe xinetd services that are also displayed by \nchkconfig\n are switched\non/off by editing configuration files and are ignored in this context.\n\n\n\n\nchanged_config_files\n\n\n\n\nContains all configuration files which have been changed since they were\ninstalled.\nChanged configuration files are all those files which are marked as such in the\npackage which has installed them. A configuration file change is reported\nif its content or its attributes like Linux permission bits or ownership\nhave changed.\n\n\n\n\nchanged_managed_files\n\n\n\n\nContains the names and contents of all non-configuration files which have\nbeen changed compared to the files in the package. A file change is reported\nif its content or its attributes like Linux permission bits or ownership\nhave changed.\n\n\n\n\nunmanaged_files\n\n\n\n\nContains the names and contents of all files which are not part of any RPM\npackage. The list of unmanaged files contains only plain files and\ndirectories. Special files like device nodes, named pipes and Unix domain\nsockets are ignored. The directories \n/tmp\n,  \n/var/tmp\n, \n/.snapshots/\n,\n\n/var/run\n and special mounts like procfs and sysfs are ignored, too.\nIf a directory is in this list, no file or directory below it belongs to a\nRPM package.\n\n\nMeta data information of unmanaged files is only available if the files were\nextracted during inspection.\n\n\nUsing the \n--extract-unmanaged-files\n option, the files are transferred from\nthe system and stored in the system description. Depending on the content of\nthe inspected system, the amount of data stored may be huge.",
             "title": "Scopes"
         },
         {
@@ -197,7 +197,7 @@
         },
         {
             "location": "/machinery-analyze.1/",
-            "text": "analyze \u2014 Analyze System Description\n\n\nSYNOPSIS\n\n\nmachinery analyze\n NAME -o | --operation=OPERATION\n\n\nmachinery\n help analyze\n\n\nDESCRIPTION\n\n\nThe \nanalyze\n subcommand analyzes an existing system description and enriches\nit with additional information. Supported operations are:\n\n\n\n\nconfig-file-diffs\n:\n    Generates the diffs between the extracted changed config files from the\n    system and the original versions from the RPM packages.\n    The diffs can be shown using \nmachinery show --show-diffs\n\n\n\n\nARGUMENTS\n\n\n\n\nNAME\n (required):\n    Name of the system description.\n\n\n\n\nOPTIONS\n\n\n\n\n-o OPERATION\n, \n--operation=OPERATION\n (required):\n    The analyze operation to perform.\n\n\n\n\nEXAMPLES\n\n\n\n\n\n\nAnalyze the config file diffs for the \nmyhost\n system description:\n\n\n$ \nmachinery\n analyze myhost --operation=config-file-diffs",
+            "text": "analyze \u2014 Analyze System Description\n\n\nSYNOPSIS\n\n\nmachinery analyze\n NAME -o | --operation=OPERATION\n\n\nmachinery\n help analyze\n\n\nDESCRIPTION\n\n\nThe \nanalyze\n subcommand analyzes an existing system description and enriches\nit with additional information. Supported operations are:\n\n\n\n\nchanged-config-files-diffs\n:\n    Generates the diffs between the extracted changed configuration files from the\n    system and the original versions from the RPM packages.\n    The diffs can be shown using \nmachinery show --show-diffs\n\n\n\n\nARGUMENTS\n\n\n\n\nNAME\n (required):\n    Name of the system description.\n\n\n\n\nOPTIONS\n\n\n\n\n-o OPERATION\n, \n--operation=OPERATION\n (required):\n    The analyze operation to perform.\n\n\n\n\nEXAMPLES\n\n\n\n\n\n\nAnalyze the config file diffs for the \nmyhost\n system description:\n\n\n$ \nmachinery\n analyze myhost --operation=changed-config-files-diffs",
             "title": "Analyze"
         },
         {
@@ -212,7 +212,7 @@
         },
         {
             "location": "/machinery-analyze.1/#description",
-            "text": "The  analyze  subcommand analyzes an existing system description and enriches\nit with additional information. Supported operations are:   config-file-diffs :\n    Generates the diffs between the extracted changed config files from the\n    system and the original versions from the RPM packages.\n    The diffs can be shown using  machinery show --show-diffs",
+            "text": "The  analyze  subcommand analyzes an existing system description and enriches\nit with additional information. Supported operations are:   changed-config-files-diffs :\n    Generates the diffs between the extracted changed configuration files from the\n    system and the original versions from the RPM packages.\n    The diffs can be shown using  machinery show --show-diffs",
             "title": "DESCRIPTION"
         },
         {
@@ -227,7 +227,7 @@
         },
         {
             "location": "/machinery-analyze.1/#examples",
-            "text": "Analyze the config file diffs for the  myhost  system description:  $  machinery  analyze myhost --operation=config-file-diffs",
+            "text": "Analyze the config file diffs for the  myhost  system description:  $  machinery  analyze myhost --operation=changed-config-files-diffs",
             "title": "EXAMPLES"
         },
         {
@@ -272,7 +272,7 @@
         },
         {
             "location": "/machinery-compare.1/",
-            "text": "compare \u2014 Compare System Descriptions\n\n\nSYNOPSIS\n\n\nmachinery compare\n [-s SCOPE | --scope=SCOPE] [-e EXCLUDE-SCOPE | --exclude-scope=EXCLUDE-SCOPE] [--no-pager] [--show-all] [--html] NAME1 NAME2\n\n\nmachinery\n help compare\n\n\nDESCRIPTION\n\n\nThe \ncompare\n command compares stored system descriptions. The scope option can\nbe used to limit the output to the given scopes.\n\n\nARGUMENTS\n\n\n\n\n\n\nNAME1\n (required):\n    First system description to compare.\n\n\n\n\n\n\nNAME2\n (required):\n    Second system description to compare.\n\n\n\n\n\n\nOPTIONS\n\n\n\n\n\n\n-s SCOPE\n, \n--scope=SCOPE\n (optional):\n    Limit output to the specified scope.\n    See the \nScope section\n for more information.\n\n\n\n\n\n\n-e SCOPE\n, \n--exclude-scope=EXCLUDE-SCOPE\n (optional):\n    Skip output of the specified scope.\n    See the \nScope section\n for more information.\n\n\n\n\n\n\n--no-pager\n (optional):\n    Do not pipe output into a pager.\n\n\n\n\n\n\n--show-all\n (optional):\n    Show also common properties of the descriptions (not only the differences).\n\n\n\n\n\n\n--html\n (optional):\n    Shows the comparison of two system descriptions in the web browser.\n\n\n\n\n\n\nEXAMPLES\n\n\n\n\n\n\nCompare system descriptions saved as \nearth\n and \nmoon\n:\n\n\n$ \nmachinery\n compare earth moon\n\n\n\n\n\n\nCompare system descriptions, but limit the scope to repositories only:\n\n\n$ \nmachinery\n compare earth moon -s repositories\n\n\n\n\n\n\nCompare lists of changed managed files and include the common ones in the\n    list:\n\n\n$ \nmachinery\n compare earth moon --scope=changed-managed-files --show-all\n\n\n\n\n\n\nCompares system descriptions and shows the result in HTML format in your web browser:\n\n\n$ \nmachinery\n compare --html earth moon",
+            "text": "compare \u2014 Compare System Descriptions\n\n\nSYNOPSIS\n\n\nmachinery compare\n [-s SCOPE | --scope=SCOPE] [-e IGNORE-SCOPE | --ignore-scope=IGNORE-SCOPE] [--no-pager] [--show-all] [--html] NAME1 NAME2\n\n\nmachinery\n help compare\n\n\nDESCRIPTION\n\n\nThe \ncompare\n command compares stored system descriptions. The scope option can\nbe used to limit the output to the given scopes.\n\n\nARGUMENTS\n\n\n\n\n\n\nNAME1\n (required):\n    First system description to compare.\n\n\n\n\n\n\nNAME2\n (required):\n    Second system description to compare.\n\n\n\n\n\n\nOPTIONS\n\n\n\n\n\n\n-s SCOPE\n, \n--scope=SCOPE\n (optional):\n    Limit output to the specified scope.\n    See the \nScope section\n for more information.\n\n\n\n\n\n\n-e SCOPE\n, \n--ignore-scope=IGNORE-SCOPE\n (optional):\n    Skip output of the specified scope.\n    See the \nScope section\n for more information.\n\n\n\n\n\n\n--no-pager\n (optional):\n    Do not pipe output into a pager.\n\n\n\n\n\n\n--show-all\n (optional):\n    Show also common properties of the descriptions (not only the differences).\n\n\n\n\n\n\n--html\n (optional):\n    Shows the comparison of two system descriptions in the web browser.\n\n\n\n\n\n\nEXAMPLES\n\n\n\n\n\n\nCompare system descriptions saved as \nearth\n and \nmoon\n:\n\n\n$ \nmachinery\n compare earth moon\n\n\n\n\n\n\nCompare system descriptions, but limit the scope to repositories only:\n\n\n$ \nmachinery\n compare earth moon -s repositories\n\n\n\n\n\n\nCompare lists of changed managed files and include the common ones in the\n    list:\n\n\n$ \nmachinery\n compare earth moon --scope=changed-managed-files --show-all\n\n\n\n\n\n\nCompares system descriptions and shows the result in HTML format in your web browser:\n\n\n$ \nmachinery\n compare --html earth moon",
             "title": "Compare"
         },
         {
@@ -282,7 +282,7 @@
         },
         {
             "location": "/machinery-compare.1/#synopsis",
-            "text": "machinery compare  [-s SCOPE | --scope=SCOPE] [-e EXCLUDE-SCOPE | --exclude-scope=EXCLUDE-SCOPE] [--no-pager] [--show-all] [--html] NAME1 NAME2  machinery  help compare",
+            "text": "machinery compare  [-s SCOPE | --scope=SCOPE] [-e IGNORE-SCOPE | --ignore-scope=IGNORE-SCOPE] [--no-pager] [--show-all] [--html] NAME1 NAME2  machinery  help compare",
             "title": "SYNOPSIS"
         },
         {
@@ -297,7 +297,7 @@
         },
         {
             "location": "/machinery-compare.1/#options",
-            "text": "-s SCOPE ,  --scope=SCOPE  (optional):\n    Limit output to the specified scope.\n    See the  Scope section  for more information.    -e SCOPE ,  --exclude-scope=EXCLUDE-SCOPE  (optional):\n    Skip output of the specified scope.\n    See the  Scope section  for more information.    --no-pager  (optional):\n    Do not pipe output into a pager.    --show-all  (optional):\n    Show also common properties of the descriptions (not only the differences).    --html  (optional):\n    Shows the comparison of two system descriptions in the web browser.",
+            "text": "-s SCOPE ,  --scope=SCOPE  (optional):\n    Limit output to the specified scope.\n    See the  Scope section  for more information.    -e SCOPE ,  --ignore-scope=IGNORE-SCOPE  (optional):\n    Skip output of the specified scope.\n    See the  Scope section  for more information.    --no-pager  (optional):\n    Do not pipe output into a pager.    --show-all  (optional):\n    Show also common properties of the descriptions (not only the differences).    --html  (optional):\n    Shows the comparison of two system descriptions in the web browser.",
             "title": "OPTIONS"
         },
         {
@@ -492,7 +492,7 @@
         },
         {
             "location": "/machinery-inspect.1/",
-            "text": "inspect \u2014 Inspect Running System\n\n\nSYNOPSIS\n\n\nmachinery inspect\n [OPTIONS] HOSTNAME\n\n\nmachinery\n help inspect\n\n\nDESCRIPTION\n\n\nThe \ninspect\n command inspects a running system and generates a system\ndescription from the gathered data.\n\n\nThe system data is structured into scopes, controlled by the\n\n--scope\n option.\n\n\nNote\n:\nMachinery will always inspect all specified scopes, and skip scopes which\ntrigger errors.\n\n\nARGUMENTS\n\n\n\n\nHOSTNAME\n (required):\n    The host name of the system to be inspected. The host name will also be\n    used as the name of the stored system description unless another name is\n    provided with the \n--name\n option.\n\n\n\n\nOPTIONS\n\n\n\n\n\n\n-n NAME\n, \n--name=NAME\n (optional):\n    Store the system description under the specified name.\n\n\n\n\n\n\n-s SCOPE\n, \n--scope=SCOPE\n (optional):\n    Inspect system for specified scope.\n    See the \nScope section\n for more information.\n\n\n\n\n\n\n-e SCOPE\n, \n--exclude-scope=EXCLUDE-SCOPE\n (optional):\n    Inspect system for all scopes except the specified scope.\n    See the \nScope section\n for more information.\n\n\n\n\n\n\n-r USER\n, \n--remote-user=USER\n (optional):\n    Defines the user which is used to access the inspected system via SSH.\n    This user needs to be allowed to run certain commands using sudo (see\n    PREREQUISITES for more information).\n    To change the default-user use \nmachinery config remote-user=USER\n\n\n\n\n\n\n-p SSH-PORT\n, \n--ssh-port SSH-PORT\n (optional):\n    Specifies the SSH port of the remote SSH server.\n\n\n\n\n\n\n-i SSH-IDENTITY-FILE\n, \n--ssh-identity-file SSH-IDENTITY-FILE\n (optional):\n    Specifies the SSH private key what should be used to authenticate with the\n    remote SSH server. Keys with a passphrase are not allowed here. Use the ssh-agent\n    instead.\n\n\n\n\n\n\n-x\n, \n--extract-files\n (optional):\n    Extract changed configuration and unmanaged files from the inspected system.\n    Shortcut for the combination of \n--extract-changed-config-files\n,\n    \n--extract-unmanaged-files\n, and \n--extract-changed-managed-files\n\n\n\n\n\n\n--extract-changed-config-files\n (optional):\n    Extract changed configuration files from the inspected system.\n\n\n\n\n\n\n--extract-unmanaged-files\n (optional):\n    Extract unmanaged files from the inspected system.\n\n\n\n\n\n\n--extract-changed-managed-files\n (optional):\n    Extract changed managed files from inspected system.\n\n\n\n\n\n\n--skip-files\n (optional):\n    Do not consider given files or directories during inspection. Either provide\n    one file or directory name or a list of names separated by commas. You can\n    also point to a file which contains a list of files to filter (one per line)\n    by adding an '@' before the path, e.g.\n\n\n$ \nmachinery\n inspect --skip-files=@/path/to/filter_file myhost\n\n\nIf a filename contains a comma it needs to be escaped, e.g.\n\n\n$ \nmachinery\n inspect --skip-files=/file\\,with_comma myhost\n\n\nNote\n: File or directory names are not expanded, e.g. '../path' is taken\n  literally and not expanded.\n\n\n\n\n\n\n--verbose\n (optional):\n    Display the filters which are used during inspection.\n\n\n\n\n\n\nPREREQUISITES\n\n\n\n\n\n\nInspecting a local system requires running \nmachinery\n as root.\n\n\n\n\n\n\nInspecting a remote system requires passwordless SSH login as root on the\n    inspected system.\n    Use \nssh-agent\n or asymmetric keys (you can transfer the current SSH key\n    via \nssh-copy-id\n to the inspected host, e.g.: \nssh-copy-id root@HOSTNAME\n)\n\n\n\n\n\n\nThe system to be inspected needs to have the following commands:\n\n\n\n\nrpm\n or \ndpkg\n\n\nzypper\n, \nyum\n, or \napt-cache\n\n\nrsync\n\n\nchkconfig\n, \ninitctl\n, or \nsystemctl\n\n\ncat\n\n\nsed\n\n\nfind\n\n\ntar\n\n\n\n\n\n\n\n\nWhen inspecting as non-root the user needs passwordless sudo rights.\n    The following entry in the sudoers file would allow the user \nmachinery\n\n    to run sudo without password input:\n\n\nmachinery ALL=(ALL) NOPASSWD: ALL\n\n\n\n\n\n\nTo add a remote \nmachinery\n user run as root:\n\n\n# \nuseradd\n -m machinery -c \"remote user for machinery\"\n\n\nTo configure a password for the new user run:\n\n\n# \npasswd\n machinery\n\n\n\n\n\n\nEXAMPLES\n\n\n\n\n\n\nInspect remote system \nmyhost\n and save system description under name\n    'MySystem':\n\n\n$ \nmachinery\n inspect --name=MySystem myhost\n\n\n\n\n\n\nInspect the installed packages of your local system and save system description\n    under the name 'localhost' (you need to become root):\n\n\n# \nmachinery\n inspect --scope=\"packages\" localhost\n\n\n\n\n\n\nExtracts changed managed files and saves them in the same way as changed\n    configuration files are saved:\n\n\n$ \nmachinery\n inspect --scope=changed-managed-files --extract-files myhost\n\n\n\n\n\n\nTo inspect the remote system \nmyhost\n with the user \nmachinery\n:\n\n\n$ \nmachinery\n inspect --remote-user machinery myhost",
+            "text": "inspect \u2014 Inspect Running System\n\n\nSYNOPSIS\n\n\nmachinery inspect\n [OPTIONS] HOSTNAME\n\n\nmachinery\n help inspect\n\n\nDESCRIPTION\n\n\nThe \ninspect\n command inspects a running system and generates a system\ndescription from the gathered data.\n\n\nThe system data is structured into scopes, controlled by the\n\n--scope\n option.\n\n\nNote\n:\nMachinery will always inspect all specified scopes, and skip scopes which\ntrigger errors.\n\n\nNote\n:\nTasks on Debian-like systems are treated as patterns.\n\n\nARGUMENTS\n\n\n\n\nHOSTNAME\n (required):\n    The host name of the system to be inspected. The host name will also be\n    used as the name of the stored system description unless another name is\n    provided with the \n--name\n option.\n\n\n\n\nOPTIONS\n\n\n\n\n\n\n-n NAME\n, \n--name=NAME\n (optional):\n    Store the system description under the specified name.\n\n\n\n\n\n\n-s SCOPE\n, \n--scope=SCOPE\n (optional):\n    Inspect system for specified scope.\n    See the \nScope section\n for more information.\n\n\n\n\n\n\n-e SCOPE\n, \n--ignore-scope=IGNORE-SCOPE\n (optional):\n    Inspect system for all scopes except the specified scope.\n    See the \nScope section\n for more information.\n\n\n\n\n\n\n-r USER\n, \n--remote-user=USER\n (optional):\n    Defines the user which is used to access the inspected system via SSH.\n    This user needs to be allowed to run certain commands using sudo (see\n    PREREQUISITES for more information).\n    To change the default-user use \nmachinery config remote-user=USER\n\n\n\n\n\n\n-p SSH-PORT\n, \n--ssh-port SSH-PORT\n (optional):\n    Specifies the SSH port of the remote SSH server.\n\n\n\n\n\n\n-i SSH-IDENTITY-FILE\n, \n--ssh-identity-file SSH-IDENTITY-FILE\n (optional):\n    Specifies the SSH private key what should be used to authenticate with the\n    remote SSH server. Keys with a passphrase are not allowed here. Use the ssh-agent\n    instead.\n\n\n\n\n\n\n-x\n, \n--extract-files\n (optional):\n    Extract changed configuration and unmanaged files from the inspected system.\n    Shortcut for the combination of \n--extract-changed-config-files\n,\n    \n--extract-unmanaged-files\n, and \n--extract-changed-managed-files\n\n\n\n\n\n\n--extract-changed-config-files\n (optional):\n    Extract changed configuration files from the inspected system.\n\n\n\n\n\n\n--extract-unmanaged-files\n (optional):\n    Extract unmanaged files from the inspected system.\n\n\n\n\n\n\n--extract-changed-managed-files\n (optional):\n    Extract changed managed files from inspected system.\n\n\n\n\n\n\n--skip-files\n (optional):\n    Do not consider given files or directories during inspection. Either provide\n    one file or directory name or a list of names separated by commas. You can\n    also point to a file which contains a list of files to filter (one per line)\n    by adding an '@' before the path, e.g.\n\n\n$ \nmachinery\n inspect --skip-files=@/path/to/filter_file myhost\n\n\nIf a filename contains a comma it needs to be escaped, e.g.\n\n\n$ \nmachinery\n inspect --skip-files=/file\\,with_comma myhost\n\n\nNote\n: File or directory names are not expanded, e.g. '../path' is taken\n  literally and not expanded.\n\n\n\n\n\n\n--verbose\n (optional):\n    Display the filters which are used during inspection.\n\n\n\n\n\n\nPREREQUISITES\n\n\n\n\n\n\nInspecting a local system requires running \nmachinery\n as root.\n\n\n\n\n\n\nInspecting a remote system requires passwordless SSH login as root on the\n    inspected system.\n    Use \nssh-agent\n or asymmetric keys (you can transfer the current SSH key\n    via \nssh-copy-id\n to the inspected host, e.g.: \nssh-copy-id root@HOSTNAME\n)\n\n\n\n\n\n\nThe system to be inspected needs to have the following commands:\n\n\n\n\nrpm\n or \ndpkg\n\n\nzypper\n, \nyum\n, or \napt-cache\n\n\nrsync\n\n\nchkconfig\n, \ninitctl\n, or \nsystemctl\n\n\ncat\n\n\nsed\n\n\nfind\n\n\ntar\n\n\n\n\n\n\n\n\nWhen inspecting as non-root the user needs passwordless sudo rights.\n    The following entry in the sudoers file would allow the user \nmachinery\n\n    to run sudo without password input:\n\n\nmachinery ALL=(ALL) NOPASSWD: ALL\n\n\n\n\n\n\nTo add a remote \nmachinery\n user run as root:\n\n\n# \nuseradd\n -m machinery -c \"remote user for machinery\"\n\n\nTo configure a password for the new user run:\n\n\n# \npasswd\n machinery\n\n\n\n\n\n\nEXAMPLES\n\n\n\n\n\n\nInspect remote system \nmyhost\n and save system description under name\n    'MySystem':\n\n\n$ \nmachinery\n inspect --name=MySystem myhost\n\n\n\n\n\n\nInspect the installed packages of your local system and save system description\n    under the name 'localhost' (you need to become root):\n\n\n# \nmachinery\n inspect --scope=\"packages\" localhost\n\n\n\n\n\n\nExtracts changed managed files and saves them in the same way as changed\n    configuration files are saved:\n\n\n$ \nmachinery\n inspect --scope=changed-managed-files --extract-files myhost\n\n\n\n\n\n\nTo inspect the remote system \nmyhost\n with the user \nmachinery\n:\n\n\n$ \nmachinery\n inspect --remote-user machinery myhost",
             "title": "Inspect"
         },
         {
@@ -507,7 +507,7 @@
         },
         {
             "location": "/machinery-inspect.1/#description",
-            "text": "The  inspect  command inspects a running system and generates a system\ndescription from the gathered data.  The system data is structured into scopes, controlled by the --scope  option.  Note :\nMachinery will always inspect all specified scopes, and skip scopes which\ntrigger errors.",
+            "text": "The  inspect  command inspects a running system and generates a system\ndescription from the gathered data.  The system data is structured into scopes, controlled by the --scope  option.  Note :\nMachinery will always inspect all specified scopes, and skip scopes which\ntrigger errors.  Note :\nTasks on Debian-like systems are treated as patterns.",
             "title": "DESCRIPTION"
         },
         {
@@ -517,7 +517,7 @@
         },
         {
             "location": "/machinery-inspect.1/#options",
-            "text": "-n NAME ,  --name=NAME  (optional):\n    Store the system description under the specified name.    -s SCOPE ,  --scope=SCOPE  (optional):\n    Inspect system for specified scope.\n    See the  Scope section  for more information.    -e SCOPE ,  --exclude-scope=EXCLUDE-SCOPE  (optional):\n    Inspect system for all scopes except the specified scope.\n    See the  Scope section  for more information.    -r USER ,  --remote-user=USER  (optional):\n    Defines the user which is used to access the inspected system via SSH.\n    This user needs to be allowed to run certain commands using sudo (see\n    PREREQUISITES for more information).\n    To change the default-user use  machinery config remote-user=USER    -p SSH-PORT ,  --ssh-port SSH-PORT  (optional):\n    Specifies the SSH port of the remote SSH server.    -i SSH-IDENTITY-FILE ,  --ssh-identity-file SSH-IDENTITY-FILE  (optional):\n    Specifies the SSH private key what should be used to authenticate with the\n    remote SSH server. Keys with a passphrase are not allowed here. Use the ssh-agent\n    instead.    -x ,  --extract-files  (optional):\n    Extract changed configuration and unmanaged files from the inspected system.\n    Shortcut for the combination of  --extract-changed-config-files ,\n     --extract-unmanaged-files , and  --extract-changed-managed-files    --extract-changed-config-files  (optional):\n    Extract changed configuration files from the inspected system.    --extract-unmanaged-files  (optional):\n    Extract unmanaged files from the inspected system.    --extract-changed-managed-files  (optional):\n    Extract changed managed files from inspected system.    --skip-files  (optional):\n    Do not consider given files or directories during inspection. Either provide\n    one file or directory name or a list of names separated by commas. You can\n    also point to a file which contains a list of files to filter (one per line)\n    by adding an '@' before the path, e.g.  $  machinery  inspect --skip-files=@/path/to/filter_file myhost  If a filename contains a comma it needs to be escaped, e.g.  $  machinery  inspect --skip-files=/file\\,with_comma myhost  Note : File or directory names are not expanded, e.g. '../path' is taken\n  literally and not expanded.    --verbose  (optional):\n    Display the filters which are used during inspection.",
+            "text": "-n NAME ,  --name=NAME  (optional):\n    Store the system description under the specified name.    -s SCOPE ,  --scope=SCOPE  (optional):\n    Inspect system for specified scope.\n    See the  Scope section  for more information.    -e SCOPE ,  --ignore-scope=IGNORE-SCOPE  (optional):\n    Inspect system for all scopes except the specified scope.\n    See the  Scope section  for more information.    -r USER ,  --remote-user=USER  (optional):\n    Defines the user which is used to access the inspected system via SSH.\n    This user needs to be allowed to run certain commands using sudo (see\n    PREREQUISITES for more information).\n    To change the default-user use  machinery config remote-user=USER    -p SSH-PORT ,  --ssh-port SSH-PORT  (optional):\n    Specifies the SSH port of the remote SSH server.    -i SSH-IDENTITY-FILE ,  --ssh-identity-file SSH-IDENTITY-FILE  (optional):\n    Specifies the SSH private key what should be used to authenticate with the\n    remote SSH server. Keys with a passphrase are not allowed here. Use the ssh-agent\n    instead.    -x ,  --extract-files  (optional):\n    Extract changed configuration and unmanaged files from the inspected system.\n    Shortcut for the combination of  --extract-changed-config-files ,\n     --extract-unmanaged-files , and  --extract-changed-managed-files    --extract-changed-config-files  (optional):\n    Extract changed configuration files from the inspected system.    --extract-unmanaged-files  (optional):\n    Extract unmanaged files from the inspected system.    --extract-changed-managed-files  (optional):\n    Extract changed managed files from inspected system.    --skip-files  (optional):\n    Do not consider given files or directories during inspection. Either provide\n    one file or directory name or a list of names separated by commas. You can\n    also point to a file which contains a list of files to filter (one per line)\n    by adding an '@' before the path, e.g.  $  machinery  inspect --skip-files=@/path/to/filter_file myhost  If a filename contains a comma it needs to be escaped, e.g.  $  machinery  inspect --skip-files=/file\\,with_comma myhost  Note : File or directory names are not expanded, e.g. '../path' is taken\n  literally and not expanded.    --verbose  (optional):\n    Display the filters which are used during inspection.",
             "title": "OPTIONS"
         },
         {
@@ -532,7 +532,7 @@
         },
         {
             "location": "/machinery-inspect-docker.1/",
-            "text": "inspect-container \u2014 Inspect Container\n\n\nSYNOPSIS\n\n\nmachinery inspect-container\n [OPTIONS] IMAGENAME\n\n\nmachinery inspect-container\n [OPTIONS] IMAGEID\n\n\nmachinery\n help inspect-container\n\n\nDESCRIPTION\n\n\nThe \ninspect-container\n command inspects a container image. It creates and starts the container from the provided image before inspection\nand generates a system description from the gathered data. After the inspection the container will be killed and removed again.\nThis approach ensures that no containers and images are affected by the inspection.\n\n\nRight now the container inspection only supports Docker images.\n\n\nThe system data is structured into scopes, controlled by the\n\n--scope\n option.\n\n\nNote\n:\nMachinery will always inspect all specified scopes, and skip scopes which\ntrigger errors.\n\n\nARGUMENTS\n\n\n\n\nIMAGENAME / IMAGEID\n (required):\n    The name or id of the image to be inspected. The provided name or id will also be\n    used as the name of the stored system description unless another name is\n    provided with the \n--name\n option.\n\n\n\n\nOPTIONS\n\n\n\n\n\n\n-n NAME\n, \n--name=NAME\n (optional):\n    Store the system description under the specified name.\n\n\n\n\n\n\n-s SCOPE\n, \n--scope=SCOPE\n (optional):\n    Inspect image for specified scope.\n    See the \nScope section\n for more information.\n\n\n\n\n\n\n-e SCOPE\n, \n--exclude-scope=EXCLUDE-SCOPE\n (optional):\n    Inspect image for all scopes except the specified scope.\n    See the \nScope section\n for more information.\n\n\n\n\n\n\n-x\n, \n--extract-files\n (optional):\n    Extract changed configuration and unmanaged files from the inspected container.\n    Shortcut for the combination of \n--extract-changed-config-files\n,\n    \n--extract-unmanaged-files\n, and \n--extract-changed-managed-files\n\n\n\n\n\n\n--extract-changed-config-files\n (optional):\n    Extract changed configuration files from the inspected image.\n\n\n\n\n\n\n--extract-unmanaged-files\n (optional):\n    Extract unmanaged files from the inspected image.\n\n\n\n\n\n\n--extract-changed-managed-files\n (optional):\n    Extract changed managed files from inspected image.\n\n\n\n\n\n\n--skip-files\n (optional):\n    Do not consider given files or directories during inspection. Either provide\n    one file or directory name or a list of names separated by commas. You can\n    also point to a file which contains a list of files to filter (one per line)\n    by adding an '@' before the path, e.g.\n\n\n$ \nmachinery\n inspect-container --skip-files=@/path/to/filter_file myimage\n\n\nIf a filename contains a comma it needs to be escaped, e.g.\n\n\n$ \nmachinery\n inspect-container --skip-files=/file\\,with_comma myimage\n\n\nNote\n: File or directory names are not expanded, e.g. '../path' is taken\n  literally and not expanded.\n\n\n\n\n\n\n--verbose\n (optional):\n    Display the filters which are used during inspection.\n\n\n\n\n\n\nPREREQUISITES\n\n\n\n\n\n\nInspecting a container requires an image specified by the name or id.\n\n\n\n\n\n\nThe image to be inspected needs to have the following commands:\n\n\n\n\nrpm\n or \ndpkg\n\n\nzypper\n, \nyum\n or \napt-cache\n\n\nrsync\n\n\ncat\n\n\nsed\n\n\nfind\n\n\n\n\n\n\n\n\nEXAMPLES\n\n\n\n\n\n\nInspect Docker container \nmyimage\n and save system description under name 'MyContainer':\n\n\n$ \nmachinery\n inspect-container --name=MyContainer myimage\n\n\n\n\n\n\nInspect Docker container \n076f46c1bef1\n and save system description under name 'MySecondContainer':\n\n\n$ \nmachinery\n inspect-container --name=MySecondContainer 076f46c1bef1\n\n\n\n\n\n\nExtract changed managed files and save them:\n\n\n$ \nmachinery\n inspect-container --scope=changed-managed-files --extract-files myimage",
+            "text": "inspect-container \u2014 Inspect Container\n\n\nSYNOPSIS\n\n\nmachinery inspect-container\n [OPTIONS] IMAGENAME\n\n\nmachinery inspect-container\n [OPTIONS] IMAGEID\n\n\nmachinery\n help inspect-container\n\n\nDESCRIPTION\n\n\nThe \ninspect-container\n command inspects a container image. It creates and starts the container from the provided image before inspection\nand generates a system description from the gathered data. After the inspection the container will be killed and removed again.\nThis approach ensures that no containers and images are affected by the inspection.\n\n\nRight now the container inspection only supports Docker images.\n\n\nThe system data is structured into scopes, controlled by the\n\n--scope\n option.\n\n\nNote\n:\nMachinery will always inspect all specified scopes, and skip scopes which\ntrigger errors.\n\n\nARGUMENTS\n\n\n\n\nIMAGENAME / IMAGEID\n (required):\n    The name or id of the image to be inspected. The provided name or id will also be\n    used as the name of the stored system description unless another name is\n    provided with the \n--name\n option.\n\n\n\n\nOPTIONS\n\n\n\n\n\n\n-n NAME\n, \n--name=NAME\n (optional):\n    Store the system description under the specified name.\n\n\n\n\n\n\n-s SCOPE\n, \n--scope=SCOPE\n (optional):\n    Inspect image for specified scope.\n    See the \nScope section\n for more information.\n\n\n\n\n\n\n-e SCOPE\n, \n--ignore-scope=IGNORE-SCOPE\n (optional):\n    Inspect image for all scopes except the specified scope.\n    See the \nScope section\n for more information.\n\n\n\n\n\n\n-x\n, \n--extract-files\n (optional):\n    Extract changed configuration and unmanaged files from the inspected container.\n    Shortcut for the combination of \n--extract-changed-config-files\n,\n    \n--extract-unmanaged-files\n, and \n--extract-changed-managed-files\n\n\n\n\n\n\n--extract-changed-config-files\n (optional):\n    Extract changed configuration files from the inspected image.\n\n\n\n\n\n\n--extract-unmanaged-files\n (optional):\n    Extract unmanaged files from the inspected image.\n\n\n\n\n\n\n--extract-changed-managed-files\n (optional):\n    Extract changed managed files from inspected image.\n\n\n\n\n\n\n--skip-files\n (optional):\n    Do not consider given files or directories during inspection. Either provide\n    one file or directory name or a list of names separated by commas. You can\n    also point to a file which contains a list of files to filter (one per line)\n    by adding an '@' before the path, e.g.\n\n\n$ \nmachinery\n inspect-container --skip-files=@/path/to/filter_file myimage\n\n\nIf a filename contains a comma it needs to be escaped, e.g.\n\n\n$ \nmachinery\n inspect-container --skip-files=/file\\,with_comma myimage\n\n\nNote\n: File or directory names are not expanded, e.g. '../path' is taken\n  literally and not expanded.\n\n\n\n\n\n\n--verbose\n (optional):\n    Display the filters which are used during inspection.\n\n\n\n\n\n\nPREREQUISITES\n\n\n\n\n\n\nInspecting a container requires an image specified by the name or id.\n\n\n\n\n\n\nThe image to be inspected needs to have the following commands:\n\n\n\n\nrpm\n or \ndpkg\n\n\nzypper\n, \nyum\n or \napt-cache\n\n\nrsync\n\n\ncat\n\n\nsed\n\n\nfind\n\n\n\n\n\n\n\n\nEXAMPLES\n\n\n\n\n\n\nInspect Docker container \nmyimage\n and save system description under name 'MyContainer':\n\n\n$ \nmachinery\n inspect-container --name=MyContainer myimage\n\n\n\n\n\n\nInspect Docker container \n076f46c1bef1\n and save system description under name 'MySecondContainer':\n\n\n$ \nmachinery\n inspect-container --name=MySecondContainer 076f46c1bef1\n\n\n\n\n\n\nExtract changed managed files and save them:\n\n\n$ \nmachinery\n inspect-container --scope=changed-managed-files --extract-files myimage",
             "title": "Inspect Docker"
         },
         {
@@ -557,7 +557,7 @@
         },
         {
             "location": "/machinery-inspect-docker.1/#options",
-            "text": "-n NAME ,  --name=NAME  (optional):\n    Store the system description under the specified name.    -s SCOPE ,  --scope=SCOPE  (optional):\n    Inspect image for specified scope.\n    See the  Scope section  for more information.    -e SCOPE ,  --exclude-scope=EXCLUDE-SCOPE  (optional):\n    Inspect image for all scopes except the specified scope.\n    See the  Scope section  for more information.    -x ,  --extract-files  (optional):\n    Extract changed configuration and unmanaged files from the inspected container.\n    Shortcut for the combination of  --extract-changed-config-files ,\n     --extract-unmanaged-files , and  --extract-changed-managed-files    --extract-changed-config-files  (optional):\n    Extract changed configuration files from the inspected image.    --extract-unmanaged-files  (optional):\n    Extract unmanaged files from the inspected image.    --extract-changed-managed-files  (optional):\n    Extract changed managed files from inspected image.    --skip-files  (optional):\n    Do not consider given files or directories during inspection. Either provide\n    one file or directory name or a list of names separated by commas. You can\n    also point to a file which contains a list of files to filter (one per line)\n    by adding an '@' before the path, e.g.  $  machinery  inspect-container --skip-files=@/path/to/filter_file myimage  If a filename contains a comma it needs to be escaped, e.g.  $  machinery  inspect-container --skip-files=/file\\,with_comma myimage  Note : File or directory names are not expanded, e.g. '../path' is taken\n  literally and not expanded.    --verbose  (optional):\n    Display the filters which are used during inspection.",
+            "text": "-n NAME ,  --name=NAME  (optional):\n    Store the system description under the specified name.    -s SCOPE ,  --scope=SCOPE  (optional):\n    Inspect image for specified scope.\n    See the  Scope section  for more information.    -e SCOPE ,  --ignore-scope=IGNORE-SCOPE  (optional):\n    Inspect image for all scopes except the specified scope.\n    See the  Scope section  for more information.    -x ,  --extract-files  (optional):\n    Extract changed configuration and unmanaged files from the inspected container.\n    Shortcut for the combination of  --extract-changed-config-files ,\n     --extract-unmanaged-files , and  --extract-changed-managed-files    --extract-changed-config-files  (optional):\n    Extract changed configuration files from the inspected image.    --extract-unmanaged-files  (optional):\n    Extract unmanaged files from the inspected image.    --extract-changed-managed-files  (optional):\n    Extract changed managed files from inspected image.    --skip-files  (optional):\n    Do not consider given files or directories during inspection. Either provide\n    one file or directory name or a list of names separated by commas. You can\n    also point to a file which contains a list of files to filter (one per line)\n    by adding an '@' before the path, e.g.  $  machinery  inspect-container --skip-files=@/path/to/filter_file myimage  If a filename contains a comma it needs to be escaped, e.g.  $  machinery  inspect-container --skip-files=/file\\,with_comma myimage  Note : File or directory names are not expanded, e.g. '../path' is taken\n  literally and not expanded.    --verbose  (optional):\n    Display the filters which are used during inspection.",
             "title": "OPTIONS"
         },
         {
@@ -722,7 +722,7 @@
         },
         {
             "location": "/machinery-show.1/",
-            "text": "show \u2014 Show System Description\n\n\nSYNOPSIS\n\n\nmachinery show\n [-s SCOPE | --scope=SCOPE] [-e EXCLUDE-SCOPE | --exclude-scope=EXCLUDE-SCOPE] [--no-pager] [--show-diffs] [--html] NAME\n\n\nmachinery\n help show\n\n\nDESCRIPTION\n\n\nThe \nshow\n command displays a stored system description.\nScopes are supported and limit the output to the given scope.\nThe hostname of the inspected system and the last modification\nin local time are shown in the title of each scope section.\n\n\nARGUMENTS\n\n\n\n\nNAME\n (required):\n    Use specified system description.\n\n\n\n\nOPTIONS\n\n\n\n\n\n\n-s SCOPE\n, \n--scope=SCOPE\n (optional):\n    Limit output to the specified scope.\n    See the \nScope section\n for more information.\n    If displaying information related to a scope fails, \nshow\n will print an error message what has failed.\n    In case of an error, no content is displayed.\n\n\n\n\n\n\n-e EXCLUDE-SCOPE\n, \n--exclude-scope=EXCLUDE-SCOPE\n (optional):\n    Skip output of the specified scope.\n    See the \nScope section\n for more information.\n\n\n\n\n\n\n--no-pager\n (optional):\n    Do not pipe output into a pager.\n\n\n\n\n\n\n--show-diffs\n (optional):\n    Include the generated diffs in the output if available (see \nmachinery help analyze\n\n    for more information).\n\n\n\n\n\n\n--html\n (optional):\n    Run a web server and open the system description in HTML format in your web browser using the\n    \nxdg-open\n command.\n\n\n\n\n\n\n--verbose\n (optional):\n    Display the filters which were applied before showing the system description.\n\n\n\n\n\n\nEXAMPLES\n\n\n\n\n\n\nShow the system description taken from the last inspection, saved as \nearth\n:\n\n\n$ \nmachinery\n show earth\n\n\n\n\n\n\nShow the system description, but limit the scope to repositories only:\n\n\n$ \nmachinery\n show earth -s repositories\n\n\n\n\n\n\nShow the list of changed managed files:\n\n\n$ \nmachinery\n show earth --scope=changed-managed-files",
+            "text": "show \u2014 Show System Description\n\n\nSYNOPSIS\n\n\nmachinery show\n [-s SCOPE | --scope=SCOPE] [-e IGNORE-SCOPE | --ignore-scope=IGNORE-SCOPE] [--no-pager] [--show-diffs] [--html] NAME\n\n\nmachinery\n help show\n\n\nDESCRIPTION\n\n\nThe \nshow\n command displays a stored system description.\nScopes are supported and limit the output to the given scope.\nThe hostname of the inspected system and the last modification\nin local time are shown in the title of each scope section.\n\n\nARGUMENTS\n\n\n\n\nNAME\n (required):\n    Use specified system description.\n\n\n\n\nOPTIONS\n\n\n\n\n\n\n-s SCOPE\n, \n--scope=SCOPE\n (optional):\n    Limit output to the specified scope.\n    See the \nScope section\n for more information.\n    If displaying information related to a scope fails, \nshow\n will print an error message what has failed.\n    In case of an error, no content is displayed.\n\n\n\n\n\n\n-e IGNORE-SCOPE\n, \n--ignore-scope=IGNORE-SCOPE\n (optional):\n    Skip output of the specified scope.\n    See the \nScope section\n for more information.\n\n\n\n\n\n\n--no-pager\n (optional):\n    Do not pipe output into a pager.\n\n\n\n\n\n\n--show-diffs\n (optional):\n    Include the generated diffs in the output if available (see \nmachinery help analyze\n\n    for more information).\n\n\n\n\n\n\n--html\n (optional):\n    Run a web server and open the system description in HTML format in your web browser using the\n    \nxdg-open\n command.\n\n\n\n\n\n\n--verbose\n (optional):\n    Display the filters which were applied before showing the system description.\n\n\n\n\n\n\nEXAMPLES\n\n\n\n\n\n\nShow the system description taken from the last inspection, saved as \nearth\n:\n\n\n$ \nmachinery\n show earth\n\n\n\n\n\n\nShow the system description, but limit the scope to repositories only:\n\n\n$ \nmachinery\n show earth -s repositories\n\n\n\n\n\n\nShow the list of changed managed files:\n\n\n$ \nmachinery\n show earth --scope=changed-managed-files",
             "title": "Show"
         },
         {
@@ -732,7 +732,7 @@
         },
         {
             "location": "/machinery-show.1/#synopsis",
-            "text": "machinery show  [-s SCOPE | --scope=SCOPE] [-e EXCLUDE-SCOPE | --exclude-scope=EXCLUDE-SCOPE] [--no-pager] [--show-diffs] [--html] NAME  machinery  help show",
+            "text": "machinery show  [-s SCOPE | --scope=SCOPE] [-e IGNORE-SCOPE | --ignore-scope=IGNORE-SCOPE] [--no-pager] [--show-diffs] [--html] NAME  machinery  help show",
             "title": "SYNOPSIS"
         },
         {
@@ -747,7 +747,7 @@
         },
         {
             "location": "/machinery-show.1/#options",
-            "text": "-s SCOPE ,  --scope=SCOPE  (optional):\n    Limit output to the specified scope.\n    See the  Scope section  for more information.\n    If displaying information related to a scope fails,  show  will print an error message what has failed.\n    In case of an error, no content is displayed.    -e EXCLUDE-SCOPE ,  --exclude-scope=EXCLUDE-SCOPE  (optional):\n    Skip output of the specified scope.\n    See the  Scope section  for more information.    --no-pager  (optional):\n    Do not pipe output into a pager.    --show-diffs  (optional):\n    Include the generated diffs in the output if available (see  machinery help analyze \n    for more information).    --html  (optional):\n    Run a web server and open the system description in HTML format in your web browser using the\n     xdg-open  command.    --verbose  (optional):\n    Display the filters which were applied before showing the system description.",
+            "text": "-s SCOPE ,  --scope=SCOPE  (optional):\n    Limit output to the specified scope.\n    See the  Scope section  for more information.\n    If displaying information related to a scope fails,  show  will print an error message what has failed.\n    In case of an error, no content is displayed.    -e IGNORE-SCOPE ,  --ignore-scope=IGNORE-SCOPE  (optional):\n    Skip output of the specified scope.\n    See the  Scope section  for more information.    --no-pager  (optional):\n    Do not pipe output into a pager.    --show-diffs  (optional):\n    Include the generated diffs in the output if available (see  machinery help analyze \n    for more information).    --html  (optional):\n    Run a web server and open the system description in HTML format in your web browser using the\n     xdg-open  command.    --verbose  (optional):\n    Display the filters which were applied before showing the system description.",
             "title": "OPTIONS"
         },
         {

data/manual/site/sitemap.xml

@@ -4,7 +4,7 @@
     
     <url>
      <loc>None/docs/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -13,25 +13,25 @@
         
     <url>
      <loc>None/machinery_main_general.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery_main_scopes.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery_main_usecases.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery_security_implications.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
@@ -41,109 +41,109 @@
         
     <url>
      <loc>None/machinery-analyze.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery-build.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery-compare.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery-config.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery-copy.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery-deploy.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery-export-autoyast.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery-export-kiwi.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery-inspect.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery-inspect-docker.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery-list.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery-man.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery-move.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery-remove.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery-serve.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery-show.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery-upgrade-format.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>None/machinery-validate.1/</loc>
-     <lastmod>2016-03-01</lastmod>
+     <lastmod>2016-04-04</lastmod>
      <changefreq>daily</changefreq>
     </url>