Hello
On Thu, Sep 1, 2016 at 3:30 PM, megha sharma wrote:
> Hello,
>
> Where can I find the output logs after running exec command on windows
> puppet agent.
Check Event Viewer of Windows.
https://docs.puppet.com/puppet/4.2/reference/services_agent_windows.html#logging
>
> Thanks,
> Megha
>
>
On Thu, Sep 1, 2016 at 3:00 AM, megha sharma wrote:
> Hello,
>
> Where can I find the output logs after running exec command on windows
> puppet agent.
>
> Thanks,
> Megha
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe fr
Hi Matt,
Thanks for your answer. I will try your module, it seems better that mine :)
But I don't think that the module is the problem, because it works fine on
all the node. Just, I don't know why, it suddenly fail, and works again
after reboot.
Anthony
Le jeudi 3 janvier 2013 16:27:40 UTC+1,
Note: I didn't follow this thread from the beginning, so this comment
might be out of place.
On Thu, Jan 3, 2013 at 8:59 AM, Anthony BRODARD
wrote:
> Hi list,
>
> I've writed this module to deploy the public key of our debian repository :
>
>> file
>> {
>> "/etc/apt/repos-public.key":
>>
Hello Bernd, thanks for the answer, but when i trie to escape the quotes
puppet print this error message:
err:
/Stage[main]/Logger/Logger::Append_if_no_such_line7[modify.profile.redhat]/Exec[Line7]/returns:
change from notrun to 0 failed: /bin/echo 'PROMPT_COMMAND\='history' >>
'/etc/profile'
First, put the whole line in single quotes in order to prevent Puppet from
trying to resolve all the dollar signs as variables. Then simply escape all
quotes within your string. I didn't test it, but this should work:
line => 'PROMPT_COMMAND=\'history -a >(tee -a ~/.bash_history | logger -t
\"
On 2012-08-01 18:47, Anton Swood wrote:
Hello all.
I have one simple question. Can I after executing manifest implement
some command on master?
You could link up to the report processor. That's triggered on the
master after a run.
Best Regards, David
--
You received this message because y
On Wed, May 30, 2012 at 2:00 PM, Ryan Coleman wrote:
> On Sun, May 27, 2012 at 1:18 PM, hohum wrote:
> > I get an error that the exec command failed because it returned 1
> instead of
> > 0 but when I copy the command puppet outputs as an error, and paste that
> > into a shell it works perfectly
On Sun, May 27, 2012 at 1:18 PM, hohum wrote:
> I get an error that the exec command failed because it returned 1 instead of
> 0 but when I copy the command puppet outputs as an error, and paste that
> into a shell it works perfectly. The command's syntax is this:
Hi,
After you run your command
