The adopted zimlet available in the [[https://github.com/Zimbra-Community/adopted|Zimbra community repository]] all now officially Zimbra Collaboration Server 8.5 now. „All“, however, is the wrong word. There are two exceptions: * The [[https://github.com/Zimbra-Community/adopted/tree/master/ca_uoguelph_ccs_coloredemailsplus|“Colored E-Mails“ zimlet]] doesn’t work in 8.5, because of a missing functionality. I’ve created bug [[https://bugzilla.zimbra.com/show_bug.cgi?id=95344|95344]] at Zimbra about this * I will deprecate the [[https://github.com/Zimbra-Community/adopted/tree/master/com_zimbra_linkedin|Linkedin-Zimlet]],
I’m currently migrating my 8.0.6 (yes, I skipped the 8.0.7 for no apparent reason!) setup to the current 8.5 and these are some notes about the changes I found: ===== Systems administrators ===== * The localconfig-variable „postfix_virtual_alias_maps“ (that allows you to alter the postfix setting „virtual_alias_maps“) doesn’t exist anymore and was moved into the main
Last week I’ve set up my new home server based on a Mac Mini and obviously Mac OS X (Mavericks). What can I say? Like I expected, everything went like a breeze… Well, until I configured my wife’s PC laptop with Windows 7. I have shared the printer to all my Macs with no problem,
I’ve done some cleanup here and removed the bilingual setup as I noticed, that I’m only writing english posts. So I threw away all the clutter (although the german version of the CV is still reachable). And I made the people sad, who like my adaption of the zenlike template, because I switched to a
This is just a short one. Based on the short script found [[http://www.linuxfromscratch.org/blfs/view/development/chapter07/network.html|in the linuxfromscratch-documentation]], I wrote this small script, that creates persistent network rules based on the pci bus. Just pipe the output to /etc/udev/rules.d/70-persistent-net.rules and edit the output there, if you want to do renaming. #!/bin/bash for dir in /sys/class/net/* ; do [
I’ve just spent some hours on investigating why the hell syslog-ng would log to two files while one logpath had the „final“-flag set. To share this lesson learned with you: The final-flag doesn’t do anything to embedded log statements. If you’ve read the syslog-ng handbook carefully (unlike me), you will already know this. Only top-level
//**AAAARGHHH!**// After a pretty nasty working expansion of the raid system of our production Zimbra server, fsck went berserk on our ext3 filesystem and reported missing inode links in various places (say „15367“ inodes). „Thankfully“ only our hsm-storage was affected. HSM is Zimbra’s way of automatically moving old messages to a cheaper and slower storage.
===== Basics ===== I’m currently fiddling around with high availability on Linux. I haven’t done this before, but a colleague of mine pointed me towards [[http://clusterlabs.org/|Pacemaker]] together with [[http://corosync.github.io/corosync/|Corosync]] (to keep things short: corosync keeps the cluster nodes in sync and pacemaker stops/starts/monitors services on the nodes). I’d like to walk you through a fairly