Re: --parse-only issues

[Edward F. Brown]

> Hey all,
>
> I was trying to find a way to check the syntax if our cfengine files
> before we commit them in cvs. So far, it appears that --parse-only only
> works on files that are in /var/cfengine. Is there a way to override
> this and specific a location on the fly? I tried looking through the
> docs, but I just didn't see anything talking about it.


'-f' allows you to specify a file name.  You need to be explicit about the
path to the file, or it defaults to inputs, as you noted.  I.e.,
'./filename', rather than just 'filename'.

Here's a script I run on cvs commit of files in the inputs directory:

--------------------------------------------------------------------
 #!/bin/sh

# cfsyn_check: called by cvs commitinfo trigger (/var/CVS/CVSROOT/commitinfo)
#              return code determines whether commit is allowed
#              only run on files ending in '.cf'

for i in "$@"
do
        if echo "$i" |grep -q "\.cf"
        then
                sudo /usr/sbin/cfagent -pf ./$i
                if [ $? -ne 0 ]
                then
                        exit 1
                fi
        fi
done
------------------------------------------------------------------

This is the commitinfo trigger (.../CVSROOT/commitinfo):

# Check cfengine syntax before allowing commit
inputs          /usr/local/sbin/cfsyn_check %s

hope this helps,
Ed