It seems that Samba 3.5 has problems binding it's socket when running on dual-stack Linux systems. This is what I am seeing in log.smbd, right after starting Samba:

[2011/11/30 18:42:18, 0] smbd/server.c:1141(main)
smbd version 3.5.11 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2011/11/30 18:42:20.269303, 0] smbd/server.c:501(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address already in use
[2011/11/30 18:42:20.269350, 0] smbd/server.c:501(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address already in use


I am seeing this on at least 3 different Linux distributions:

• CentOS 6.0 x86_64, samba-3.5.4-68.el6_0.2.x86_64
• Gentoo 10.0 x86_64, net-fs/samba-3.5.11

Have you ever noticed that if you put cron jobs in /etc/cron.daily on a SLES machine, they seem to run at random times? I noticed it a few times, and I find it to be really annoying. Say, I rebooted a machine yesterday around 14:00, and today at 14:15, the machine starts rebuilding the man db, backing up the rpm db, cleaning /tmp, rotating logs, etc. Huh?! Looks like a bad idea to do such things when the system is currently in use by multiple people. Imagine that you put a database backup in there, and that backup locks your database...

Well, this actually is a feature. If you read /etc/sysconfig/cron, you'll find this piece of text:

# At which time cron.daily should start. Default is 15 minutes after booting
# the system. Example setting would be "14:00".

In case you're annoyed by the fact that backspace doesn't work by default in vim on SLES, add this to /etc/vimrc or ~/.vimrc:


set backspace=indent,eol,start