I don’t know if you’ve write with emacs/vim or any other classical tool editor, a manifest or a Puppet module. If you did it, I’m pretty sure you’ve made a lot of syntax errors or got errors during catalog compilation. During a long time, I was using Geppetto to help me on writing and suggesting better syntax to my manifest.
I took the latest available version of Geppetto but it crashes all the time.
Awesome is still my window manager and I still love it. With my laptop, I need to be able to quickly get my working environment when I power it on. The major problem I had was to avoid having the same opened windows at boot if I’m in the train, at work or at home. Of course there is no GPS in the laptop to detect my location, so I couldn’t set a rule for it.
I didn’t really play with Puppet since a long time and a lot of things have changed.
I’m currently writing a Puppet module for MySecureShell. And the thing is, it’s hard to quickly find the relevant information on how to build a module from scratch. I like to have experience return and what a chance when I saw a tweet regarding it, the same day as I started to write the module :-)
As I’m new to LXC, I am discovering how it works, see the maturity of the project and it’s integration in Debian. I’ve made a post a few weeks ago to introduce the basics and now I’m digging in advanced features.
I’ve encountered several issues. Most of them are not critical but unfortunately looks like a lack of integration on Debian.
The first one is related to wheezy template and I’ve already talked about it in a previous post.
I recently discovered that repository that looks correctly maintained and often updated.
I like this repository as it’s updated faster than the Debian one and you can have the latest version of some packages. Of course you can do package pinning if you only want one or a set of packages.
You can access to the repository here : http://www.dotdeb.org/
Glances is a cross-platform curses-based monitoring tool written in Python.
It avoids to run several tools to get a all in one overview of your system. For example, when you want to quickly see what’s wrong on a system for diagnosis, you’ll need to launch top/htop, iostat, vmstat…Glances gives you a large overview of your system health.
You can then investigate with the appropriate tool if you want. But you didn’t waste your time in opening several tools to get the first desired information : where does the problem comes from ?
The goal of this documentation is how to quickly setup a monitoring screen machine for Nagios/Shinken. Several times in several company I had to do that kind of thing. On Mac OS and Linux.
I finished to create a documentation for the next times I’ll have to deploy such things. The idea is to have a machine that nobody never touch once installed. It’s always boring to plug a keyboard and a mouse when somethings goes wrong on this kind of machine that you normally never have to touch.