Bloody cluster solutions (continued)
So, as the previous try on getting the teamix people to fix the bloody LoadBalancer (as in sending at least an identification string for the SSH check) didn’t work so well (they told me, I should configure MASQ uerading/ ROUTE ing on the PacketPro(which is kinda icky), I went on today and looked at what SLES10 installs as default logger. Surprisingly they install a rather new syslog-ng (well, syslog-ng-1.6.8 is what they ship) so it was rather easy to workaround the situation. ...