On Thu, Sep 17, 2009 at 10:39 AM, Nigel Kersten <nig...@google.com> wrote:
>
>
> On Thu, Sep 17, 2009 at 6:26 AM, John Ingersoll <jh.ingers...@gmail.com>wrote:
>
>> Hi,
>>
>> I have an exec {} that runs a command line script, for which 0 and 1 are
>> both good return codes. (Specifically, spamassassin update; 1 means no new
>> downloads). I tried
>>
>> returns => [0,1],
>>
>> but it still reports an error on RC = 1. Are multiple values not
>> appropriate here?
>>
>> My workaround is to exec a wrapper script that traps '1' and returns 0.
>>
>
>
> Is this on 0.25.0?
>
no, we're still on 0.24.8
>
> 0.24.8 doesn't support multiple return codes, although it would be a
> trivial patch to backport.
>
Thanks, guess I'm ok for now, though.
> Another workaround is to or with true that we've done sometimes
>
> command => "/usr/bin/foo || true",
>
> but that's more of a sledgehammer than specifying acceptable return codes.
>
Yes, actually I _want_ notification for RC > 1
Thank you
--
John Ingersoll, Jr.
Linux Sysadmin
University of Georgia, Athens
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
