TaxMe 2008 auf Ubuntu jaunty 9.04 amd64

The saga continues.

Nun ja,wir kennen das Muster mitlerweile: ein neues TaxMe, einen neuen Tag mit herumpröbeln verloren.

Warum schaffen es DV Informatik auch nach 4 Jahren nicht eine Version von TaxMe herauszugeben, ”’die einfach läuft”’? Man nimmt die auf dem Desktop mit Abstand verbreitetste Linux Distribution, startet Taxme und - es tut nicht.

So sieht meine TaxMe2008 Installation aus:

  # apt-get install libswt-gtk-3.4-java libswt-gtk-3.4-java-gcj libswt-gtk-3.4-jni
  $ cd TaxMe2008/libs
  $ mv linux-gtk linux-gtk.32bit
  $ mkdir linux-gtk
  $ for i in \
    libswt-atk-gtk-3448.so \
    libswt-awt-gtk-3448.so \
    libswt-cairo-gtk-3448.so \
    libswt-gnome-gtk-3448.so \
    libswt-gtk-3448.so \
    libswt-mozilla-gtk-3448.so \
    libswt-pi-gtk-3448.so \
    do; 
       ln -s /usr/lib/jni/$i
    done
   $ ln -s /usr/share/java/swt-gtk-3.4.jar swt.jar
   $ cat runTaxMe
   #!/bin/sh
   export MOZILLA_FIVE_HOME=/usr/lib/xulrunner
   export LD_LIBRARY_PATH=${MOZILLA_FIVE_HOME}:${LD_LIBRARY_PATH}
   ./TaxMeBe2008

Resultat:

• TaxMe2008 startet
• Hilfe nicht verfügbar

$ cat log.txt
        at ch.dvbern.tax.common.presentation.cd.util.BrowserUtil.createBrowser(BrowserUtil.java:76)                 
        at ch.dvbern.tax.common.presentation.cd.Taxme.createWelcomeContent(Taxme.java:323)                          
        at ch.dvbern.tax.common.presentation.cd.Taxme.createContents(Taxme.java:313)                                
        at org.eclipse.jface.window.Window.create(Window.java:431)                                                  
        at ch.dvbern.tax.common.presentation.cd.TaxmeController.startup(TaxmeController.java:911)                   
        at ch.dvbern.tax.common.presentation.cd.TaxmeLauncher$1.run(TaxmeLauncher.java:145)                         
        at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)                                           
        at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133)                             
        at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3378)                                      
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3036)                                       
        at ch.dvbern.tax.common.presentation.cd.TaxmeLauncher.launchApplication(TaxmeLauncher.java:155)             
        at ch.dvbern.tax.common.presentation.cd.TaxmeLauncher.launchTaxme(TaxmeLauncher.java:86)                    
        at ch.dvbern.tax.be.np.presentation.cd.TaxmeBeLauncher.main(TaxmeBeLauncher.java:82)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:616)
        at ch.dvbern.lib.update.Launcher.main(Launcher.java:91)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:616)
        at com.zerog.lax.LAX.launch(DashoA8113)
        at com.zerog.lax.LAX.main(DashoA8113)
Caused by: org.eclipse.swt.SWTError: XPCOM error -1041039359
        at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:1597)
        at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:355)
        at org.eclipse.swt.browser.Browser.(Browser.java:118)
        at ch.dvbern.tax.common.presentation.cd.util.BrowserUtil.createBrowser(BrowserUtil.java:58)
        ... 23 more
org.eclipse.swt.SWTError: XPCOM error -1041039359
        at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:1597)
        at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:355)
        at org.eclipse.swt.browser.Browser.(Browser.java:118)
        at ch.dvbern.tax.common.presentation.cd.help.gui.HelpApplication.createContents(HelpApplication.java:171)
        at org.eclipse.jface.window.Window.create(Window.java:431)
        at ch.dvbern.tax.common.presentation.cd.action.menu.HelpMainhelpAction.openHelpWindow(HelpMainhelpAction.java:79)
        at ch.dvbern.tax.common.presentation.cd.action.menu.HelpMainhelpAction.run(HelpMainhelpAction.java:51)
        at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
        at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583)
        at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500)
        at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033)

Und es ist notabene nach 4 Jahren immer noch das gleiche Problem: den Browser mit den externen Hilfetexten zu starten.

Occassionaly we’ve been seeing messages like:

spam acl condition: error reading from spamd socket: Connection reset by peer

in /var/log/exim4/paniclog

But lately the problem has become much more persistent. I found out, that there’s some arsehole spammer sending us 500K spams every ca. 70 minutes. From /var/log/mail.log:

Jul 17 08:52:32 mail spamd[477]: spamd: identified spam (7.9/5.0) for spamd:1004 in 288.5 seconds, 505669 bytes.

Now since spamassassin would take that long (nearly 5 minutes!!!) to find out whether that mail is a spam or not, exim would simply timeout it’s connection to spamassassin and the result was the message seen above.

What I did was to use sa-compile to compile the SA rules to “native code” and to enable “Rule2XSBody”, which on Debian lives in /etc/spamassassin/v320.pre.

This seems to make SA quite a lot faster and to use less CPU.

If this won’t help we could also restrict the maximum size of messages to scan.

Yours Tomáš Pospíšek

Die internationale Open Source GIS-Konferenez FOSS4G findet dieses Jahr vom 6.-9. September 2010 in Barcelona statt.

Sourcepole ist mit drei Vorträgen vertreten:

• Comparison of Open Source Virtual Globes
• Performance and statistical analysis of WMS servers
• SpatiaLite, the Shapefile of the future?

Zusätzlich unterstützen wir den QGIS-Workshop und nehmen mit dem QGIS-Mapserver an WMS Performance Shootout teil.

Since I found Michel de Boer’s explanation of many of the fundamental SIP concepts in his 2005 dutch presentation of the Twinkle SIP phone very short and easy to follow - contrary to a lot of other material about SIP out there - I’ve translated it to english.

Here it is: Twinkle - a SIP softphone for Linux

Well, sometimes one wonders why people write tools that wheight a megabyte, when it’s easy to stick together one or two tools with a script and have the same thing.

Here’s a ruby script that generates a ping latency graph (target is google):

#!/usr/bin/ruby
#
# based on
#   http://oss.oetiker.ch/rrdtool/prog/rrdruby.en.html example
# with help of the tutorial
#   http://oss.oetiker.ch/rrdtool/tut/rrdtutorial.en.html
# and the docu
#   http://oss.oetiker.ch/rrdtool/doc/rrdcreate.en.html
# 
# placed in the public domain by Tomáš Pospíšek

require "RRD"

$rrd    = `mktemp /tmp/tmp.XXXXXXXX`.chomp
$grafik = `mktemp /tmp/tmp.XXXXXXXX`.chomp
$start  = 0

def now()
  Time.now.to_i
end

def create()
  $start=now()
  RRD.create(
    $rrd,
    "--start", "#{$start - 1}",
    "--step", "#{1}",       # every 1s
    "DS:pinglatency:GAUGE:10:0:200", # 10s of missing data are OK, min=0, max=200 (ping time)
    "RRA:AVERAGE:0.5:1:#{60*30}") # 60 seconds * 30 minutes
  puts "RRD database created #{$rrd} at #{$start}"
  puts "Your graph is at #{$grafik}"
end

def ping_latency
   `ping -c 1 -n -w 1 google.com` =~ /.* time=(\d+)/
  # 64 bytes from 74.125.43.147: icmp_seq=1 ttl=52 time=31.6 ms
  return $1
end

def update()
  puts "updating #{$rrd} with #{now()}:#{ping_latency()}"
  RRD.update($rrd, "#{now()}:#{ping_latency()}")
end

def generate_gfx()
  # puts "generating graph #{$grafik}"
  RRD.graph(
   "#{$grafik}",
    "--title", " Ping latency to Google",
    "--x-grid", "SECOND:10:MINUTE:1:MINUTE:2:0:%X",
    "--start", $start.to_s,
#    "--end", # -> now
    "--interlace",
    "--imgformat", "PNG",
    "--width=450",
    "DEF:pinglatency=#{$rrd}:pinglatency:AVERAGE",
    "AREA:pinglatency#00b6e4:ms")
end

#main
create()
while(true)
  update()
  generate_gfx()
  sleep 1
end

It generates a graph like this:

Das erste deutschsprachige QGIS User Meeting in Bern war mit rund 80 Teilnehmern ein grosser Erfolg.

Die Folien der Präsentation des OpenLayers-Plugin sind hier erhältlich.

Die gesammelten Präsentation werden auf der QGIS-Homepage veröffentlicht.