Hi,
pinoyskull wrote:
> I tried to run it both ways, background and not, still the same issue.
You're assuming the OUI (runInstaller) is actually reporting a problem
when it exits. This is not always the case. I would recommend not
running runInstaller directly with exec{}. Rather, wrap it int
I tried to run it both ways, background and not, still the same issue.
Peter Meier wrote:
>> but when checking the processlist, runInstaller is not there
>
> Hmm, why do you send the installer to the background? The whole idea of
> puppet is that it manages the state of your resources. In your c
> but when checking the processlist, runInstaller is not there
Hmm, why do you send the installer to the background? The whole idea of
puppet is that it manages the state of your resources. In your case this
is now the resource oracle which should be in the state "installed"
(maybe even more, but
This is the log snippet that says my command executed successfully
--begin--
Sat Oct 17 18:02:24 + 2009 //Node[basenode]/oraclecube/Exec[sh
/mnt/oracle-installation/database/runInstaller -silent
-ignoreDiskWarning -responsefile
/mnt/oracle-installation/database/oracle-11g_SE.rsp &] (debug
> Yes, it did return exit 0, that's why it's weird
well, then it's rather a weird behavior of your cmd.
cheers pete
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send
Yes, it did return exit 0, that's why it's weird
Peter Meier wrote:
>> I have an exec command that executed successfully, but when checking the
>> processes it did not run the command.
>
> version etc?
>
> If puppet tells you that the exec ran successfully the cmd exited with
> exit code 0.
> I have an exec command that executed successfully, but when checking the
> processes it did not run the command.
version etc?
If puppet tells you that the exec ran successfully the cmd exited with
exit code 0.
cheers pete
--~--~-~--~~~---~--~~
You received t
