[Top][All Lists]

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

cfengine 2 migration issues

From: Ruben van Staveren
Subject: cfengine 2 migration issues
Date: Thu, 12 Feb 2004 12:03:53 +0100
User-agent: Mutt/1.5.4i

Hello all,

At RIPE NCC we have deployed a network of 60 so called Test Traffic
Measurement boxes (http://www.ripe.net/ttm/) and are currently in the progress
of upgrading our network from cfengine 1 to cfengine 2. We have encountered a
few peculiarities which weren't there in the previous versions.

cfengine 2 is now installed on our FreeBSD 4.x based Test Traffic Measurement
Testboxes, with the following remarks:

- We are using version 2.0.6 instead of the latest version available because
  the grammar in the .l and the .y files changed in 2.0.7, causing harmless
  but noisy error messages to appear when using a SetOptionString

        address@hidden:102] /tmp/cfe2/cfengine-2.0.7/src/cfagent -n -DCRON -f
        cfengine:tt97: Regular expression error 14 for 
        cfengine:tt97: empty (sub)expression

  It could be that the BSD implementation of the regular expression library is
  more strict and this error is not triggered on other platforms.

- Separate binaries for root and a non privileged maintenance account have
  been installed, this is due to the fact the cfengine status directory
  (LogDirectory) is not run time adjustable anymore. See
  what was wrong with the cfengine 1 way of doing things ?
  We use a setup where cfengine is run from cron, and not from the cfengine

- There seems to be a problem with the umask setting, we have to readjust
  permissions on files generated from programs under cfengine 2 control which
  was not needed in cfengine 1

Kind Regards,
        Ruben van Staveren

Ruben van Staveren                      RIPE Network Coordination Centre
New Projects Group/TTM                  Singel 258 Amsterdam NL
http://www.ripe.net                     +31 20 535 4444

Attachment: pgpBUUlIWqmC0.pgp
Description: PGP signature

reply via email to

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