The Linux Manuals (man pages) document is an important part of Linux documents. Linux Manuals are organized as several sections. Each section has a group of commands for a specific area in Linux usage, administration or development.
puppetca_selinux – Security Enhanced Linux Policy for the puppetca processes Description Security-Enhanced Linux secures the puppetca processes via flexible mandatory access control. The puppetca processes execute with the puppetca_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. For example: ps -eZ | grep…
– Synopsis Stand-alone certificate authority. Capable of generating certificates but mostly meant for signing certificate requests from puppet clients. Usage puppetca [-h|–help] [-V|–version] [-d|–debug] [-v|–verbose] [-g|–generate] [-l|–list] [-s|–sign] [-r|–revoke] [-p|–print] [-c|–clean] [–verify] [host] Description Because the puppetmasterd daemon defaults to not signing client certificate requests, this script is available for signing outstanding requests. It can…
puppetagent_selinux – Security Enhanced Linux Policy for the puppetagent processes Description Security-Enhanced Linux secures the puppetagent processes via flexible mandatory access control. The puppetagent processes execute with the puppetagent_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. For example: ps -eZ | grep…
puppet_selinux – Security Enhanced Linux Policy for the puppet processes Description Security-Enhanced Linux secures the puppet processes via flexible mandatory access control. The puppet processes execute with the puppet_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. For example: ps -eZ | grep…
puppet See ‘puppet help’ for help on available puppet subcommands
puppet-status – View puppet server status. Synopsis puppet status action [–terminus TERMINUS] [–extra HASH] Options Note that any configuration parameter that’s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action. For example, server and run_mode are valid configuration parameters, so you…
puppet-secret_agent – Mimics puppet agent. Synopsis puppet secret_agent action Description This subcommand currently functions as a proof of concept, demonstrating how the Faces API exposes Puppet’s internal systems to application logic; compare the actual code for puppet agent. It will eventually replace puppet agent entirely, and can provide a template for users who wish to…
puppet-resource_type – View classes, defined resource types, and nodes from all manifests. Synopsis puppet resource_type action [–terminus TERMINUS] [–extra HASH] Description This subcommand reads information about the resource collections (classes, nodes, and defined types) available in Puppet’s site manifest and modules. It will eventually be extended to examine native resource types. Options Note that any…
puppet-resource – The resource abstraction layer shell Synopsis Uses the Puppet RAL to directly interact with the system. Usage puppet resource [-h|–help] [-d|–debug] [-v|–verbose] [-e|–edit] [-H|–host host] [-p|–param parameter] [-t|–types] type [name] [attribute=value …] Description This command provides simple facilities for converting current system state into Puppet code, along with some ability to modify the…
puppet-report – Create, display, and submit reports. Synopsis puppet report action [–terminus TERMINUS] [–extra HASH] Options Note that any configuration parameter that’s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action. For example, server and run_mode are valid configuration parameters, so…
puppet-queue – Queuing daemon for asynchronous storeconfigs Synopsis Retrieves serialized storeconfigs records from a queue and processes them in order. Usage puppet queue [-d|–debug] [-v|–verbose] Description This application runs as a daemon and processes storeconfigs data, retrieving the data from a stomp server message queue and writing it to a database. For more information, including…
puppet-plugin – Interact with the Puppet plugin system. Synopsis puppet plugin action Description This subcommand provides network access to the puppet master’s store of plugins. The puppet master serves Ruby code collected from the lib directories of its modules. These plugins can be used on agent nodes to extend Facter and implement custom types and…
puppet-parser – Interact directly with the parser. Synopsis puppet parser action Options Note that any configuration parameter that’s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action. For example, server and run_mode are valid configuration parameters, so you can specify –server…
puppet-node – View and manage node definitions. Synopsis puppet node action [–terminus TERMINUS] [–extra HASH] Description This subcommand interacts with node objects, which are used by Puppet to build a catalog. A node object consists of the node’s facts, environment, node parameters (exposed in the parser as top-scope variables), and classes. Options Note that any…
puppet-module – Creates, installs and searches for modules on the Puppet Forge. Synopsis puppet module action [–environment production ] [–modulepath $confdir/modules:/usr/share/puppet/modules ] Description This subcommand can find, install, and manage modules from the Puppet Forge, a repository of user-contributed Puppet code. It can also generate empty modules, and prepare locally developed modules for release on…
puppet-master – The puppet master daemon Synopsis The central puppet server. Functions as a certificate authority by default. Usage puppet master [-D|–daemonize|–no-daemonize] [-d|–debug] [-h|–help] [-l|–logdest file|console|syslog] [-v|–verbose] [-V|–version] [–compile node-name] Description This command starts an instance of puppet master, running as a daemon and using Ruby’s built-in Webrick webserver. Puppet master can also be managed…
puppet-man – Display Puppet manual pages. Synopsis puppet man action Description This subcommand displays manual pages for all Puppet subcommands. If the ronn gem (https://github.com/rtomayko/ronn/) is installed on your system, puppet man will display fully-formated man pages. If ronn is not available, puppet man will display the raw (but human-readable) source text in a pager….
puppet-kick – Remotely control puppet agent Synopsis Trigger a puppet agent run on a set of hosts. Usage puppet kick [-a|–all] [-c|–class class] [-d|–debug] [-f|–foreground] [-h|–help] [–host host] [–no-fqdn] [–ignoreschedules] [-t|–tag tag] [–test] [-p|–ping] host [host […]] Description This script can be used to connect to a set of machines running ‘puppet agent’ and trigger…
puppet-key – Create, save, and remove certificate keys. Synopsis puppet key action [–terminus TERMINUS] [–extra HASH] Description This subcommand manages certificate private keys. Keys are created automatically by puppet agent and when certificate requests are generated with ‘puppet certificate generate’; it should not be necessary to use this subcommand directly. Options Note that any configuration…
puppet-instrumentation_probe – Manage instrumentation probes. Synopsis puppet instrumentation_probe action [–terminus TERMINUS] [–extra HASH] Description This subcommand enables/disables or list instrumentation listeners. Options Note that any configuration parameter that’s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action. For example, server and…