Cfengine Goodies

To content | To menu | To search

Monday 5 March 2012

new hard classes [arch]

By Bernard on Monday 5 March 2012, 17:32

in order to make a difference between native 32 et 64 architectures :

"32_bit", "64_bit"

from : source trunk
http://source.cfengine.com/websvn/diff.php?repname=Cfengine+core&path=%2Ftrunk%2Fsrc%2Fenv_context.c&rev=4121&peg=4121

no comment no trackback

Monday 20 February 2012

le port de cfengine

By Bernard on Monday 20 February 2012, 06:58

Le client cf-agent utilise /etc/services pour avoir le port tcp cfengine.
Le nom du service est defini dans cf.defs.h:#define CFENGINE_SERVICE "cfengine"
Pour paramétrer un port client different :
. definir CFENGINE_SERVICE "cfengine3"
. definir le port de cfengine3 dans /etc/services

merci a cyril jovet pour la lecture du code.

one comment no trackback

Monday 13 February 2012

About

By cyril on Monday 13 February 2012, 16:44

CFEngine Goodies

All Q&As on this site were selected from cfengine.com.

If you could not find the answer here, then we recommend you post your question at https://cfengine.com/forum/

All NEWs on this site were selected from cfengine COPBL & Core sources : http://source.cfengine.com/websvn/

no comment no trackback

updates and failsafe.cf

By cyril on Monday 13 February 2012, 16:04

question.png Shouldn't the copy go the other way around?

I'm a little confused about the update process for binaries. I'm using the latest svn. It looks like the included failsafe.cf will constantly overwrite any updates I install in /usr/local/sbin because of the following:

  "/usr/local/sbin"                                                            
                                             
          comment => "Ensure cfengine binaries were copied to /usr/local/sbin",
           handle => "update_files_usr_local_sbin",
            perms => u_m("755"),
        copy_from => u_cp_nobck("$(sys.workdir)/bin"),
      file_select => u_cf3_files,
     depth_search => u_recurse("1"),
           action => u_immediate;

Shouldn't the copy go the other way around? Everything else seems so well thought out I thought I'd ask here before fixing it.

Overall though, I love the new bootstrap process.

Asked by elwood

answer.png

Basically it puts a copy of /var/cfengine/bin files to /usr/local/sbin, which is the expected behaviour. A reason behind this is to have all cf-* binaries available in $PATH for the convenience.

One would argue that it would be enough to have a symlinks in /usr/local/sbin pointing back to /var/cfengine/bin. Probably it would, but for the time being it's the full copy.

Answered by Mikhail Gusarov

http://www.mail-archive.com/help-cfengine@cfengine.org/msg08617.html

no comment no trackback