facter(8) [debian man page]
FACTER(8) System Manager's Manual FACTER(8) NAME
facter - Collect and display facts about the system SYNOPSIS
facter [options] [fact] ... DESCRIPTION
facter collects and displays facts about the current system. The library behind Facter is easy to expand, making Facter an easy way to collect information about a system from within the shell or within Ruby. If no facts are specifically asked for, then all facts will be returned. OPTIONS
These programs follow the usual GNU command line syntax, with long options starting with two dashes (`-'). A summary of options is included below. --yaml Emit facts in YAML format. --json Emit facts in JSON format. --puppet Load the Puppet libraries, thus allowing Facter to load Puppet-specific facts. --help Show summary of options. --version Show version of program. --debug Enable debugging. --trace Enable backtraces. --timing Enable timing. EXAMPLES
facter Display a list of all facts facter kernel Display the kernel fact SEE ALSO
puppet(8), The facter homepage <http://www.puppetlabs.com/puppet/related-projects/facter/> AUTHOR
facter was written by Luke Kanies This manual page was written by Stig Sandbeck Mathisen <ssm@debian.org>, for the Debian project (and may be used by others). COPYRIGHT
Facter is Copyright (c) 2011 Puppet Labs, Inc Licensed under the Apache 2.0 license June 17, 2011 FACTER(8)
Check Out this Related Man Page
PUPPET-SECRET_AGENT(8) Puppet manual PUPPET-SECRET_AGENT(8) NAME
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 implement agent-like functionality with non-standard application logic. 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 is a valid configuration parameter, so you can specify --server <servername> as an argument. See the configuration file documentation at http://docs.puppetlabs.com/references/stable/configuration.html for the full list of acceptable parameters. A commented list of all configuration options can also be generated by running puppet with --genconfig. --mode MODE The run mode to use for the current action. Valid modes are user, agent, and master. --render-as FORMAT The format in which to render output. The most common formats are json, s (string), yaml, and console, but other options such as dot are sometimes available. --verbose Whether to log verbosely. --debug Whether to log debug information. ACTIONS
synchronize - Run secret_agent once. SYNOPSIS puppet secret_agent DESCRIPTION Mimics a single run of puppet agent. This action does not currently daemonize, but can download plugins, submit facts, retrieve and apply a catalog, and submit a report to the puppet master. RETURNS Verbose logging from the completed run. When used from the Ruby API: returns a Puppet::Transaction::Report object. NOTES This action requires that the puppet master's auth.conf file allow save access to the facts REST terminus. Puppet agent does not use this facility, and it is turned off by default. See http://docs.puppetlabs.com/guides/rest_auth_conf.html for more details. EXAMPLES
synchronize Trigger a Puppet run with the configured puppet master: $ puppet secret_agent COPYRIGHT AND LICENSE
Copyright 2011 by Puppet Labs Apache 2 license; see COPYING Puppet Labs, LLC June 2012 PUPPET-SECRET_AGENT(8)