#9 Single (--init) database across farm?


Is it possible to generate a database on one server and
use this database on multiple servers? If so, how?

We have an image server on a private network which we
build all of our production boxes on using System
Imager. All of these boxes then are "cookie cutter",
so theoretically, we could place the database on each
server before it gets connected to the wire and then
generate the keys for each server. Also, the database
of the "clean" server could be compared against
production servers that are already live to insure that
those servers are in compliance. Thanks for any
assistance or pointers that you can provide.


  • Ron Forrester

    Ron Forrester - 2001-08-28

    Logged In: YES

    You can definitely do this -- the key is to not monitor certain attributes which are possibly
    different, like inodes, and possibly device numbers.

    If you are sure the boxes are identical, create a policy file for one, monitoring the appropriate attributes.
    Then copy the files (the .pol, .db, .cfg files) to the tripwire installations on each machine. Better yet, put
    those files (the db and pol file) on a CD which can be mounted on every machine, and point the local cfg file
    at the mount with those files. This way they are only in one place, and cannot be modified.

    Let me know if you have other questions.

  • Ron Forrester

    Ron Forrester - 2005-06-01
    • status: open --> closed
  • Ron Forrester

    Ron Forrester - 2005-06-01

    Logged In: YES

    Marked closed in preparation for new source release which
    addresses many if not all outstanding support requests.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks