Sponsored Content
Full Discussion: Patch Administration
Operating Systems Linux Ubuntu Patch Administration Post 302417941 by techlinux on Saturday 1st of May 2010 02:42:21 PM
Old 05-01-2010
Check out Cfengine or Puppet
 

7 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

Sys Administration

What happend to the Administration board, How come no one posts there? (1 Reply)
Discussion started by: tovsky
1 Replies

2. UNIX for Dummies Questions & Answers

Remote administration

Is there a way to do remote administration on my Sun/Solaris 2.5? I have a server that is running an old copy of ARCServe 2.2 and I need to do monthly administration on it. The only way to use it is from the server so I want to use a VNC type product to do it. Since I know zip about unix, I am... (1 Reply)
Discussion started by: athpam
1 Replies

3. IP Networking

Patch-o-matic (patch for iptable) for linux2.4.08 & iptable1.2.7a

Hello friends I'm running Redhat 9.0 with linux kernel 2.4.20-8 & have iptables version 1.2.7a & encountering a problem that I narrate down. I need to apply patch to my iptable and netfilter for connection tracking and load balancing that are available in patch-o-matic distribution by netfilter.... (0 Replies)
Discussion started by: Rakesh Ranjan
0 Replies

4. UNIX for Dummies Questions & Answers

User Administration

I have an application that runs on Unix and the user administration is managed at a Unix level. The application has an application ID which is linked to the user ids which are created at Unix level. Can you please help if I can be able to track which user used the Application ID and what action was... (0 Replies)
Discussion started by: Kopano
0 Replies

5. Solaris

user administration

hi ' i am creating a primary group and a secondary group for a user. #groupadd -g 101 test #groupadd -g 102 test1 #useradd -d /export/home/user1 -m -s /bin/ksh -g test -G test user1 in /etc/passwd i can find the username as user1 and group name as test and where can i find the... (4 Replies)
Discussion started by: madhudeepan
4 Replies

6. Shell Programming and Scripting

User administration

Dear All, I need to restrict the users in our server. 1.History & history -c command working all groups & others.So i need to restrict history -c option for groups & others . 2.Any option available to view user activity with all Eg--->user1 Jul22 10:20:11 date 3.Any other Special... (7 Replies)
Discussion started by: kpoobathi
7 Replies

7. Solaris

Centralizing Administration

Hi guys. I work in an environment that caters to 150 + Solaris servers. I was wondering whether there is an application/Software that can be used to centralize Administration. e.g. If a new member comes into the team , I am required to go onto every server and create his login. Is there a system... (1 Reply)
Discussion started by: Junaid Subhani
1 Replies
PUPPET-DOC(8)							   Puppet manual						     PUPPET-DOC(8)

NAME
puppet-doc - Generate Puppet documentation and references SYNOPSIS
Generates a reference for all Puppet types. Largely meant for internal Puppet Labs use. USAGE
puppet doc [-a|--all] [-h|--help] [-o|--outputdir rdoc-outputdir] [-m|--mode text|pdf|rdoc] [-r|--reference reference-name] [--charset charset] [manifest-file] DESCRIPTION
If mode is not 'rdoc', then this command generates a Markdown document describing all installed Puppet types or all allowable arguments to puppet executables. It is largely meant for internal use and is used to generate the reference document available on the Puppet Labs web site. In 'rdoc' mode, this command generates an html RDoc hierarchy describing the manifests that are in 'manifestdir' and 'modulepath' configu- ration directives. The generated documentation directory is doc by default but can be changed with the 'outputdir' option. If the command is run with the name of a manifest file as an argument, puppet doc will output a single manifest's documentation on stdout. OPTIONS
--all Output the docs for all of the reference types. In 'rdoc' mode, this also outputs documentation for all resources. --help Print this help message --outputdir Used only in 'rdoc' mode. The directory to which the rdoc output should be written. --mode Determine the output mode. Valid modes are 'text', 'pdf' and 'rdoc'. The 'pdf' mode creates PDF formatted files in the /tmp direc- tory. The default mode is 'text'. In 'rdoc' mode you must provide 'manifests-path' --reference Build a particular reference. Get a list of references by running 'puppet doc --list'. --charset Used only in 'rdoc' mode. It sets the charset used in the html files produced. --manifestdir Used only in 'rdoc' mode. The directory to scan for stand-alone manifests. If not supplied, puppet doc will use the manifestdir from puppet.conf. --modulepath Used only in 'rdoc' mode. The directory or directories to scan for modules. If not supplied, puppet doc will use the modulepath from puppet.conf. --environment Used only in 'rdoc' mode. The configuration environment from which to read the modulepath and manifestdir settings, when reading said settings from puppet.conf. Due to a known bug, this option is not currently effective. EXAMPLE
$ puppet doc -r type > /tmp/type_reference.markdown or $ puppet doc --outputdir /tmp/rdoc --mode rdoc /path/to/manifests or $ puppet doc /etc/puppet/manifests/site.pp or $ puppet doc -m pdf -r configuration AUTHOR
Luke Kanies COPYRIGHT
Copyright (c) 2011 Puppet Labs, LLC Licensed under the Apache 2.0 License Puppet Labs, LLC June 2012 PUPPET-DOC(8)
All times are GMT -4. The time now is 12:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy