RE: Upgrade issues..

[Larson, Ryan B]

That fails because it doesn't actually expand the variable in place.  So instead of looking for the script in /etc/cfengine/inputs/foc/commands, it looks in //commands/gateway.  Plus it doesn't send the ${defaultgw} arguement either.

 

Ryan Larson
Unix Administrator
Office 312.362.3311
Cell 773.814.0938
Goldman Sachs Execution and Clearing, LP

 

---

From: Martin, Jason H [mailto:address@hidden
Sent: Tuesday, October 25, 2005 3:34 PM
To: Larson, Ryan B; address@hidden
Subject: RE: Upgrade issues..

I believe a workaround is to do:

okgw = ( ReturnsZero(/${cfimports}/commands/gateway ${defaultgw} ) )

Double /'s won't hurt anything.

 

-Jason Martin

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Larson, Ryan B
Sent: Tuesday, October 25, 2005 1:30 PM
To: address@hidden
Subject: Upgrade issues..

I am trying to upgrade from 2.1.15 to 2.1.16, but it seems that you can no longer pass variables to the command line in the groups section.

I have attached an example that works on 2.1.15 and fails on 2.1.16.

Was this just a fluke that it worked before, or did something break in the new version?

This is the error I receive now.

cf:cfengine::/tmp/cftest/cfagent.conf:10: ExecResult(/command) must specify an absolute path

<<cfagent.conf.txt>>

Ryan Larson
Unix Administrator
Office 312.362.3311
Cell 773.814.0938
Goldman Sachs Execution and Clearing, LP