pfacter 1.13-3

Pfacter is a cross-platform distribution for retrieving facts about the system it is run on. It works like a rosetta stone, collecting information on things like IP and MAC addresses, DIMMs, processors, and other hardware information. Pfacter supports writing to an LDAP database, making it an ideal tool in the creation of a universal infrastructure host list.<br /><br />OPTIONS :<br /><br />--debug<br /><br /> Print debugging information while working.<br />--help<br /><br /> Display a short usage synopsis.<br />--version<br /><br /> Display the current version/release of Pfacter.<br />--moduledir<br /><br /> Specifies the extensible module location; if no specific facts are specified, the entire moduledir directory will be read and acted upon.<br /><br /> This (at the most basic level) addes a path to perl's @INC array; as an example, if moduledir is specified as "/etc/pfacter/modules" (the default), a module named Pfacter::thirdparty would be loaded from a module located at /etc/pfacter/modules/Pfacter/thirdparty.pm.<br />--multi<br /><br /> Allows for multi-valued facts (ipAddress, macAddress, memory, etc) to be displayed as such (both locally and in LDAP).<br />--write<br /><br /> Write any new or changed host facts to LDAP. Requires that either a configuration file be specified, or a username, password, and server address be provided on the command line.<br /><br /> The following flags are used in conjunction with the --write option:<br /><br /> --configfile <configfile><br /><br /> The file containing configuration information (username, password, LDAP server address, etc). Format is:<br /><br /> $option: "value"<br /><br /> Anything specified on the command-line (such as moduledir, LDAP connection information, etc) can be specified in this configuration file.<br /><br /> For LDAP authentication, the configfile would contain something like:<br /><br /> $username: "pfacter"<br /> $password: "pf4ct3r"<br /> $server: "ldap.company.com"<br /><br /> If you use the configfile option it is also possible to specify multiple LDAP servers to attempt binds against. Simple change the format to:<br /><br /> @server: "ldap1.company.com ldap2.company.com ldap3.company.com"<br /><br /> ...and Net::LDAP will attempt to bind to each host in order until a successful connection is made. This is not possible if the server is specified on the command line.<br /><br /> The configfile flag is the most secure (and preferred) method for storing connection and authentication information. It is however possible to pass configuration information via the command line with the following three flags:<br /> --username <username><br /><br /> The name of the LDAP user to bind as.<br /> --password <password><br /><br /> Password.<br /> --server <server><br /><br /> The IP address or name of the LDAP server.<br /><br /> Refer to the examples for more information regarding the syntax/use of the username, password, and server flags.<br /> --base <base DN><br /><br /> If not specified, the base DN is guessed based on the domain.<br /> --ssl<br /><br /> Connect securely (with SSL, obviously) to the LDAP server.<br /><br />--xml<br /><br /> Print all output in XML format.<br />--yaml<br /><br /> Print all output in YAML format.

Requirements:	No special requirements
Platforms:	*nix, Linux
Keyword:	Address,  Authentication,  Command,  Configfile,  Configuration,  Connection,  Display,  Facts,  Flags,  Format,  Information,  Module,  Moduledir,  Option,  Password,  Print,  Server,  Username
Users rating:	0/10