On Mar 20, 2009, at 10:00 AM, Peter Meier wrote:
HiI just though of another case where this would be useful, running 'newaliases' after /etc/mail/aliases has been updated. What do other people do? I have mailalias { foo: ... notify => [ Exec[newaliases] ] } on each mailalias type. I thought last night that: Mailalias { notify => [ Exec[newaliases] ] } would work, but it does not seem to.this should do it. but this definition should be included as first, before any the other Mailalias definitions. I have plenty of such statements, and they work fine. Another thing is to add a wrapper define, which will set the appropriate defaults on your exec. Actually for the alias type I do it that way.
What version? I'm running 0.24.7. I have other resource defaults, and they did work. I have not tested it lately. I have defined the Mailalias within the 'mail' class and I'm testing in my 'ssh::client' class. The mail is imported before ssh and the mail class is included before the ssh::client class.
- JimP --- @(#) $Id: dot.signature,v 1.15 2007/12/27 15:06:13 pirzyk Exp $ __o j...@pirzyk.org ------------------------------------------- _'\<,_ (*)/ (*) I'd rather be out biking.
PGP.sig
Description: This is a digitally signed message part