help-cfengine
[Top][All Lists]
Advanced

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

Re: bootstrapping cfengine.


From: Chip Seraphine
Subject: Re: bootstrapping cfengine.
Date: Tue, 25 Nov 2003 13:39:18 -0600
User-agent: KMail/1.5

Not having dependencies in cfengine and core admin tools is good, as Luke 
pointed out earlier.  If one of the purposes of a tool is to help the system 
recover from some calamity (down network, misconfiguration, hosed 
environment, whatever) then the fewer assumptions you make about the state of 
the system, the better. 

The downside is that your executables are bigger, but I've found that if I run 
strip(1) on them the difference between a dynamically-linked and a 
staticically-linked executable is often only a few hundred k.

On Tuesday 25 November 2003 13:11, Christian Pearce wrote:
> That is an interesting concept.  I have an automated process for building
> packages.  I was actually able to get the makefile editing to work.  It
> seems to me that automake and autoconf with a sprinkle of libtool should be
> able to handle this better.  But what do I know.  I certainly see value in
> being able to install the cfengine package and not have any dependencies. 
> It is nice to just drop a package on the box with no other worries.  Thanks
> for the input Chip.
>
> --
> Christian Pearce
> http://www.commnav.com
>
> On Nov 25, 2003, Chip Seraphine wrote:
> > For what it's worth, I generally do things the lazy way-- tell configure
> > to look in some sandbox library directory, and populate it only with the
> > .a files.  No muss, no fuss, no makefile editing.
> >
> > On Monday 24 November 2003 14:31, oearcec wrote:
> > > "Luke A. Kanies" <address@hidden> wrote in message
> > > news:<address@hidden>...
> > >
> > > > Static linking is your friend, especially when it comes to your core
> > > > management tools.  Really.
> > > >
> > > > Now that each machine has the other's public key, just run cfagent
> > > > and the client (as long as you've got update.conf), and it should all
> > > > work fine from there.  If you haven't statically linked, this is a
> > > > much bigger pain, so I _really_ recommend static links.
> > >
> > > Luke,
> > >
> > > I have read a little bit on Google Groups about doing a static
> > > compile.  But I didn't come up with anything that worked completely.
> > > So far I did the edit the configure script by hand, replacing the
> > > -l{db,crypto} with static libraries.  But this didn't work on all the
> > > binaries.  Only cfagent, and cfservd.  There must be a better way.
> > > What method did you use to get a static build?
> > >
> > > Christian
> > > _______________________________________________
> > > Help-cfengine mailing list
> > > address@hidden
> > > http://mail.gnu.org/mailman/listinfo/help-cfengine





reply via email to

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