don't worry dear – it's just coincidence


sudo sed -i 's/karmic/lucid/g' /etc/apt/sources.list && sudo aptitude update && sudo aptitude dist-upgrade


tired to export display settings maually before using X exports?

try adding this to your “~/.bashrc”

if [ -z "$DISPLAY" ]; then
if [ `ps -awwwux|grep  X11.app |grep -vc grep` -gt 0 ]; then
export DISPLAY=":0.0"
fi
fi


Excerpt from Viscosity Support Forums:

Problem is, I want the standard 192.168.x.x and the 10.x.x.x networks to be routed locally, not through the VPN.

Try the following:

1. Go to the Viscosity menu, select Preferences, and Edit your connection
2. Click on the networking tab
3. Click the small “+” button in the Routing section to add a new route
4. Enter a Route/IP of “192.168.0.0″ (no quotes). Enter a submask of “255.255.0.0″. Enter a gateway of “net_gateway”. Click the Add button.
5. Repeat steps 3 and 4, expect with a Route/IP of “10.0.0.0″, and a submask of “255.0.0.0″
6. Click the Save button and try connecting.

The “net_gateway” command instructs the traffic to be routed through your normal local gateway rather than through the VPN connection.

Wanted: files with 0660, directories with 770

Config:

• create mask = 660
• directory mask = 770
• force create mode = 660
• force directory mode = 770

Problem: OS X clients creates

• files with 644 or 764 or 600
• directories with 2700 or 0770 or 0700

Solution:

unix extensions = no

in smb.conf on server

After updating a Domino Server from 8.0 to 8.0.2 on RHEL and installation of the german language pack, the console.log looked very strange:

30.09.2008 16:18:53   33:02
ConvertZoneToText: Warning Time Zone -1 not found!
30.09.2008 16:18:53   33:14
ConvertZoneToText: Warning Time Zone -1 not found!

After a little research the problem cleared up: domino is missing ressource files for the servers default language. This was solved after the correct language was set in the rc_script:

DOMINO_LANG="de_DE.UTF-8"