Well it turned out to be a problem with the formatting cfengine was looking for. What we are trying to do is allow for very easy building of 3rd party software that we have to build from source. Now what I am doing is creating small shell scripts that are synced via cfengine that execute when the software isn't installed. Building on my original question, is there a better way to build source code, or is that probably going to be the best option? I have to build about 30-40 different pieces of software on each host I manage/
-----Original Message----- From: Aleksey Tsalolikhin [mailto:atsaloli.t...@gmail.com] Sent: Tuesday, May 24, 2011 11:46 AM To: Scott Dobner Cc: help-cfengine@cfengine.org Subject: Re: Lengthy in-line bash commands On Tue, May 24, 2011 at 5:30 AM, Scott Dobner <scott.dob...@sas.com> wrote: > Here it is. I think I am starting to see the problem with this. I don't > have a lot of shell scripting experience, and I think the script I sent out > previously is not exactly a shell script. > > bundle agent install_xinstall > { > classes: > "xinstall_exists" expression => > fileexists("/usr/local/src/xinstall"); > commands: > !xinstall_exists:: > "<this is where I would put my command from below>"; } Got it. What your script is trying to accomplish? What is the desired end state of the system? Are you installing some 3rd party software? in-house software? It's not available as a package? As far as Cfengine grammar goes, to use a pipeline in a command, tell Cfengine to use a shell, for example: body common control { inputs => { "/var/cfengine/inputs/cfengine_stdlib.cf" }; } bundle agent example { commands: "/bin/echo hello > /tmp/test.out; /bin/echo world >> /tmp/test.out" contain => in_shell; } You can try containing your command in a shell, but if that does not work, please answer my questions above. Best, -at _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
