Apparently, deleting the cfengine_lock_db in /var/cfengine silenced the errors ... so maybe it was just an errant state setting that didn't get corrected. Problem fixed, anyway.Klaus
On 5/3/06, Klaus Steden <[EMAIL PROTECTED]> wrote:
Hmm, curious ... I've got two shell commands that generate output
Hmm, curious ... I've got two shell commands that generate output -
'makemap' and 'newaliases', but they are only generating messages to
stdout, which end up in /dev/null ... what is baffling is the fact 20
other machines run the exact same script just as often, and haven't
started spitting out any
On Mon, May 01, 2006 at 07:26:24PM -0700, Klaus wrote:
> cfengine:vfxws12:/library/cfengine/cf.X11:
>
> -- cut --
> This is the -only- machine running cfagent that spits out this message,
> and I can't figure out a how or why it's generating it. Can anyone shed
> some more light on the problem?
Do
I'm getting a strange error from one of my nodes running cfengine. It's
a Linux host (one of 50) running the same cfengine scripts from cron
like this:
-- cut --
CFBIN=/var/cfengine/bin
CFINPUTS=/var/cfengine/inputs
0 * * * * $CFBIN/cfagent --file $CFINPUTS/update.conf 1>/dev/null
-- cut --
Norma
