I started the day with ssl issues using puppet. Last week I cleaned 2 hosts in our tree using the puppet command

# puppet node clean [hostname]

on the puppetmaster. I did this to clean out the stored configs for those nodes.

But I didn't realized this also cleaned out the ssl certificates for those clients. So I started the new week with this uncomfortable issue:

[root@agent ~]# puppet agent --test err: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked warning: Not using cache on failed …

Recently we installed a Lacie Network Space 2 at home. Easy to share documents on the LAN network, having a central place for common media etc. After playing around with it I wanted to see if it's possible to gain access to the underlying operating system of it. On that way I could for example use this access to wake up a pc with wake on LAN.

And guess what, it can be done and thanks to a script of a guy Andreus it's even very easy! I found a forum post about his work and tested it successfully with …

Mumble is an open source, low-latency, high quality voice chat software primarily intended for use while gaming.

Puppet is a tool designed to manage the configuration of Unix-like and Microsoft Windows systems decoratively.

The puppet-mumble module installs a mumble server (version 1.2.3) automatically on a CentOS 6.x machine using the puppet software based on mumble-documentation.

The module needs a repository which contains the mumble-server package. I distribute this package on my own visibilityspots repository.

Using puppet this will create the necessary mumble user and group and will configure the mumble-server using your desired settings, like username, password …

It isn't supported by default using Ubuntu but it's as handy as hell, the apple infrared remote control. After some mayor headaches I finally succeeded to configure it manually on my MacBook Pro 3.1 running Ubuntu 10.04.

It's quite easy once you know how.

Installation of the lirc library:

$ sudo apt-get install lirc

Adapting the configuration files (make sure to backup them first!):

$ sudo cp /old/file /new/file.bak

/etc/lirc/hardware.conf

# /etc/lirc/hardware.conf # #Chosen Remote Control REMOTE="Apple Mac mini USB IR Receiver" REMOTE_MODULES="uinput" REMOTE_DRIVER="macmini" REMOTE_DEVICE="/dev/usb/hiddev0" REMOTE_SOCKET="" REMOTE_LIRCD_CONF …

It's rather simple, but I used to look for it a while when writing my first bash/python scripts. Wanted to typing in one command so I would need to type in every time the whole path to my newly written script.

That way routine tasks could be called much faster and easier. This can be done by creating a symlink to your /usr/bin directory:

ln -s /path/to/your/script /usr/bin/nameOfTheOverallCommmandYouWantToUseForYourScript

The most recommended permissions for files and directories on the web are 0755 and 0644. If you have shell access to your webserver you can set those permissions using those commands:

find -type d -print0 | xargs -0 chmod 755
find -type f -print0 | xargs -0 chmod 644

To monitor the different resources of my local system I use conky. After you installed the conky software you can start with the configuration of it.

$ apt-get install conky conky-colors

After I adapted the configuration my desktop became like this:

At the left side there is a pane which only monitors my system resources. The config file for it, conkyrc should be placed in your home directory as a hidden file (naming it .conkyrc).

When you now type in conky in your terminal, you should see appearing the pane on your desktop:

On the right bottom I created an rss …