Auch dieses Jahr ist Sourcepole an der deutschsprachigen FOSSGIS-Konferenz vertreten. Die FOSSGIS 2010 findet vom 2.-5. März 2010 in Osnabrück statt. Sourcepole ist mit drei Vorträgen vertreten: GIS mit Ruby on Rails Performance und Verfügbarkeit von WMS-Servern SpatiaLite, das Shapefile der Zukunft? Vorinformation: Die internationale Open Source GIS-Konferenez FOSS4G findet dieses Jahr vom 6.-9. September 2010 in Barcelona statt. Read on

Here’s a patch: # diff -u multi_http_responsetime.orig multi_http_responsetime --- multi_http_responsetime.orig 2010-02-01 10:13:22.000000000 +0100 +++ multi_http_responsetime 2010-02-01 10:30:23.000000000 +0100 @@ -16,6 +16,9 @@ use Time::HiRes qw( time ); use IO::Socket; +$FAILED=0; +$INFINITE=999999; + # ----- config ----- push(@url_array, "http://www.google.de"); push(@url_array, "http://www.t-online.de"); @@ -34,7 +37,7 @@ PeerPort => 80, Proto => 'tcp' ); - return(0) unless ($sock); + return($FAILED) unless ($sock); print $sock "GET $baseurl HTTP/1.1\nHost: $vhost\nConnection: close\n\n"; while (<$sock>) { $data . Read on

Since upgrading to Karmic I had the problem under Ubuntu that SIP calls under Twinkle would start get all chopped up every few minutes. Turns out it’s NetworkManager that scans the wireless spectrum every two minutes for networks even if you are allready connected to some AP. While people seem to be fixing the problem in the proper way, by making scanning interfere less with an active connection, there’s a good soul that provides patched versions of NetworkManager that gives up scanning while there’s an active connection to an AP. Read on

It can be integrated in any Rack based appication. Sample configuration for Ruby on Rails: config.middleware.use Rack::Monitor, :url => '/rack_status', :watch => ['/', '/ping'] The collected statistical values can be accessed at /rack_status. It is recommended to limit access to this path with our contributed middleware Rack::Access from rack-contrib. Sample munin output: Read on

In https://bugs.launchpad.net/bugs/509411 I had the problem, that locking the screen would just not work any more. It turned out that gnome-screensaver must be perpetualy runnung in the background in order to be able to lock the screen. Also this would affect the computer not locking the screen when suspending. It might be that Gnome/Ubuntu are user-friendly, however the bloat is starting to annoy me. Why do I need to be running 214 processes, when the only thing that is actually being used is firefox and a terminal? Read on