[Puppet Users] Managing sudo via puppet using #includedir

2011-08-01 Thread treydock
Is anyone having success with #includedir option in sudo?  I have a
module that uses a definition to create files in /etc/sudoers.d/ which
is referenced in the main suders file as #includedir /etc/sudoers,
but these entries are not getting referenced when sudo is used.

I'm running CentOS 5 and 6, which which sudo-1.7.2p1 and sudo-1.7.2p2
respectively.

Here's a weird symptom the problem I'm having...

# visudo -c -f /etc/sudoers.d/zabbix-puppet
 /etc/sudoers.d/zabbix-puppet: syntax error near line 0 
parse error in /etc/sudoers.d/zabbix-puppet near line 0

(((NOTE: I made absolutely no changes , just did :q)))
# visudo -f /etc/sudoers.d/zabbix-puppet
 /etc/sudoers.d/zabbix-puppet: syntax error near line 0 


# visudo -c -f /etc/sudoers.d/zabbix-puppet
/etc/sudoers.d/zabbix-puppet: parsed OK

This is my sudoers file...



## Sudoers allows particular users to run various commands as
## the root user, without needing the root password.
##
## Examples are provided at the bottom of the file for collections
## of related commands, which can then be delegated out to particular
## users or groups.
##
## This file must be edited with the 'visudo' command.

## Host Aliases
## Groups of machines. You may prefer to use hostnames (perhaps using
## wildcards for entire domains) or IP addresses instead.
# Host_Alias FILESERVERS = fs1, fs2
# Host_Alias MAILSERVERS = smtp, smtp2

## User Aliases
## These aren't often necessary, as you can use regular groups
## (ie, from files, LDAP, NIS, etc) in this file - just use
%groupname
## rather than USERALIAS
# User_Alias ADMINS = jsmith, mikem


## Command Aliases
## These are groups of related commands...

## Networking
# Cmnd_Alias NETWORKING = /sbin/route, /sbin/ifconfig, /bin/ping, /
sbin/dhclient, /usr/bin/net, /sbin/iptables, /usr/bin/rfcomm, /usr/bin/
wvdial, /sbin/iwconfig, /sbin/mii-tool

## Installation and management of software
# Cmnd_Alias SOFTWARE = /bin/rpm, /usr/bin/up2date, /usr/bin/yum

## Services
# Cmnd_Alias SERVICES = /sbin/service, /sbin/chkconfig

## Updating the locate database
# Cmnd_Alias LOCATE = /usr/bin/updatedb

## Storage
# Cmnd_Alias STORAGE = /sbin/fdisk, /sbin/sfdisk, /sbin/parted, /sbin/
partprobe, /bin/mount, /bin/umount

## Delegating permissions
# Cmnd_Alias DELEGATING = /usr/sbin/visudo, /bin/chown, /bin/chmod, /
bin/chgrp

## Processes
# Cmnd_Alias PROCESSES = /bin/nice, /bin/kill, /usr/bin/kill, /usr/bin/
killall

## Drivers
# Cmnd_Alias DRIVERS = /sbin/modprobe

# Defaults specification

#
# Disable ssh hostname sudo cmd, because it will show the password
in clear.
# You have to run ssh -t hostname sudo cmd.
#
## Defaultsrequiretty

#
# Preserving HOME has security implications since many programs
# use it when searching for configuration files.
#
Defaultsalways_set_home

Defaultsenv_reset
Defaultsenv_keep =  COLORS DISPLAY HOSTNAME HISTSIZE INPUTRC
KDEDIR LS_COLORS
Defaultsenv_keep += MAIL PS1 PS2 QTDIR USERNAME LANG LC_ADDRESS
LC_CTYPE
Defaultsenv_keep += LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT
LC_MESSAGES
Defaultsenv_keep += LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER
LC_TELEPHONE
Defaultsenv_keep += LC_TIME LC_ALL LANGUAGE LINGUAS _XKB_CHARSET
XAUTHORITY

#
# Adding HOME to env_keep may enable a user to run unrestricted
# commands via sudo.
#
# Defaults   env_keep += HOME

# Defaultssecure_path = /sbin:/bin:/usr/sbin:/usr/bin


## Next comes the main part: which users can run what software on
## which machines (the sudoers file can be shared between multiple
## systems).
## Syntax:
##
##  userMACHINE=COMMANDS
##
## The COMMANDS section may have other options added to it.
##
## Allow root to run any commands anywhere
rootALL=(ALL)   ALL



## Allows members of the 'sys' group to run networking, software,
## service management apps and more.
# %sys ALL = NETWORKING, SOFTWARE, SERVICES, STORAGE, DELEGATING,
PROCESSES, LOCATE, DRIVERS

## Allows people in group wheel to run all commands
%wheel  ALL=(ALL)   ALL

## Same thing without a password
# %wheelALL=(ALL)   NOPASSWD: ALL

## Allows members of the users group to mount and unmount the
## cdrom as root
# %users  ALL=/sbin/mount /mnt/cdrom, /sbin/umount /mnt/cdrom

## Allows members of the users group to shutdown this system
# %users  localhost=/sbin/shutdown -h now

#includedir /etc/sudoers.d


And this is the /etc/sudoers.d/zabbix-puppet

zabbix ALL=NOPASSWD: /var/lib/zabbix/bin/start_puppet

What's so strange is if I take that exact line, and put it in /etc/
sudoers , it works just fine.  So I know the syntax and such is
correct, however it doesn't get called via #includedir.

Thanks
- Trey

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 

Re: [Puppet Users] Managing sudo via puppet using #includedir

2011-08-01 Thread Len Rugen
It's working here for RHEL 5  6.  Check the owner and perms of sudoers.d,
that's probably not your problem, but it's the only one we've had.

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.



Re: [Puppet Users] Managing sudo via puppet using #includedir

2011-08-01 Thread vagn scott

On 08/01/2011 01:41 PM, treydock wrote:

#includedir /etc/sudoers.d
   


Maybe without the quotation marks?

--
vagn

--
You received this message because you are subscribed to the Google Groups Puppet 
Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.