HI,
All our unix boxes under puppet are configured with the 'mailalias' resource
type as in :
mailalias { "root":
recipient => "linuxr...@fqdn",
ensure => present
}
The majority of those boxes however don't have /etc/aliases served out by
puppet, rather, they simply have the installed default /etc/aliases locally.
I'm working on a couple of boxes within that set that have custom
/etc/aliases served out from puppet, and have with that a notify => Exec
[newaliases]. No problem there.
It's being reported that the other unix boxes aren't getting their
/etc/aliases.db rebuild when /etc/aliases changes. I'm guessing that just
having the newalias type doesn't ensure the newaliases command gets run.
If that's true, should I have another exec { "othernewaliases": with
something like onlyif => [test /etc/aliases -nt /etc/aliases.db ] ?
Or rather insist that all such boxes have their aliases file maintained by
Puppet?
Thanks
--
John Ingersoll, Jr.
Usage: fortune -P [] -a [xsz] [Q: [file]] [rKe9] -v6[+] dataspec ...
inputdir
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
