[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug w/ cfengine Log, Lock and Repositories directives
From: |
Chris Edillon |
Subject: |
Re: Bug w/ cfengine Log, Lock and Repositories directives |
Date: |
Wed, 20 Jun 2001 23:05:20 -0400 (GMT+4) |
On Wed, 20 Jun 2001, Greg Gallagher wrote:
> Dear Cfengine mailing list,
>
> I haven't even looked into this to see if the documentation says
> anything about this, but I may have found a small bug with the
> cfengine configuration file parsing. The actionsequence position in
> the cfengine.conf file will inhibit the LockDirectory and LogDirectory
> directives (at least, didn't test the others yet) from being seen.
>
[snip]
>
> Also, I'm not sure why but I _have_ to define those Lock and Log
> directives in order to keep the last.* files out of my INPUTS
> directory. I had compiled cfengine like so:
>
> ./configure --prefix=/opt/cfengine --with-lockdir=/var/run \
> --with-logdir=/var/adm/cfengine --datadir=/etc
>
> So it doesn't seem like I should have to, but for some reason the
> binary didn't have them hardcoded even with the configure.
>
which version of cfengine? IIRC versions prior to 1.6.2 would
ignore both compile-time and run-time (cfengine.conf) settings for
lockdir and logdir in favor of a hardcoded /etc/cfengine.
chris