Does anyone have advice on such a beast? I would prefer not to have to install additional software on my AIX machines, so etckeeper isn't ideal. It's also not centralized, based on my quick reading.

Ideally, I would like something that runs under Linux, logs into a list of named servers, pulls down a list of named files (per server) or all the contents of named directories (per server), perhaps does some cleanup/processing, and then stuffs them into svn. 'Centralized' is important, because if I care about a new file or directory, I don't want to have to log into 40 AIX servers to change a config file.

And I know that Chef or Puppet or cfengine would make this easier by putting the deployment under management, not just recording what was deployed after the fact. Trying to get one of those packages tested and approved on our production AIX boxes would not be easy; I'm looking for quick wins, as the kids say.


If you can store the "file list" on the central server, you can simply make different modules in rancid that will have the file list there and commands to run. It will login, run the commands, save them, and then you can post-process it in the module as well. I'm not sure why rancid wouldn't work.


Take another look at etckeeper. You'll need to add some additional scripting to push to a centralized location, but it should fit pretty well with what you're looking for. I don't think you'll find a good solution that lets you avoid software installs completely.


I'm sure you've already thought of this, but rsync over SSH with ssh key-based authentication would seem to be the answer to your question.

  • That would involve making and maintaining local rsync scripts on each AIX server, and keeping them updated individually. Also managing the slurping of those files into svn. RANCID already does this all of this for network gear out of the box, that's why I referenced it. I would ideally like something easy and centralized. Your suggestion would accomplish the end goal, but I'd honestly prefer to do less work; that's why I'm asking if there's something out there already to do the bulk of this work. – mfinni Aug 10 '11 at 16:54
  • The only thing you'd have to maintain locally on each server would be ssh keys. Specifying individual directories to rsync would likely be just as complicated to maintain as some tool that needs to be told which configuration files to track. Then end of your rsync script would just have an svn commit command. Easy peasy. – JakePaulus Aug 10 '11 at 17:37
  • Oh, I see. You mean to fire off the rsync from the central server, not from each AIX machine. My bad. – mfinni Aug 10 '11 at 17:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.