[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Parsing issue with 2.1.0.p1

From: Chip Seraphine
Subject: Parsing issue with 2.1.0.p1
Date: Tue, 04 Nov 2003 13:34:11 -0600
User-agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.2.1) Gecko/20030121

I'm upgrading from 2.0.6 -> 2.1.0p1 and found a nuisance issuye with the new parser.

In the past, I have been able to do this:

                some_sunonly_command = ( /path/to/command )
                AddClasses = ( run_some_command )

                "$(some_sunonly_command) arg1 arg2"

Since only Sun machines are running the command path'd in the some_sunonly_command variable, I have never needed to define the var on other platforms. Now, however, when I run this script on a !sunos machine, I get ye olde "absolute path" issue:

cf:cfengine::/var/cfengine/inputs/cf.main:1428: scripts or commands must have absolute path names cfengine: concerns: $(coreadm) -g '/var/core/core.%f.%u-%p' -e log -e global -d process
cfengine:beer::Execution terminated after parsing due to errors in program

I hacked around it by prefixing the variable expansion with a slash, or by defining a bogus path on non-Sun machines. But it would be much nicer if the parser would just not worry about the absolute-pathness of commands that aren't being run :-)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]