openldap logs

to have a separate logfile for openldap add to /etc/rsyslog.conf:
local4.* /var/log/openldap.log
touch /var/log/openldap.log
/etc/init.d/rsyslog restart

to have the logfile in the logrotation add a config file to /etc/logrotate.d/ :

/var/log/openldap.log
{
rotate 7
daily
missingok
notifempty
delaycompress
compress
postrotate
invoke-rc.d rsyslog reload > /dev/null
endscript
}

to change the loglevel edit /etc/ldap/slapd.d/cn\=config.ldif :

olcLogLevel: 256

hello lion, hello ssd, hello quickness

after i mounted the new disk, removed the dvd drive, i build a lion usb install device and did a clean install on the ssd, switched the user directory on my old -now second- harddisk. now the boot time for the 10,5 mbp is about 25 sec. installed xcode with the app store + macports for my linux stuff. some small fixes to get vim working correctly (arrow keys, backspace/delete problems):

:set backspace=2
:set nocompatible

the system is much faster, though there is a sata2 bus and the ssd could do sata3 …

 

 

ibm ds4700 / logical drive not on preferred path

a ibm ds4700 with four exp 810 units lost it`s preferred path setting for one controller /some logical drives. consequences : there were some machines with non-redundant paths connected to the san – these machines lost their mounted luns.(datastore for a mail machine, datastore for a fileserver with 14TB…) first i changed on the fibre channel switch fabric the zoneing to the healthy controller and remounted the drives to get the server systems back on production. after some research i seems to be clear that the solution is just only to map the logical drives back to the preferred controller/path … *sigh you can change the controller settings for the logical drives under production scenario. learned: do *all* fc/san connections redundant – don`t save money on your fibrechannel san design … ๐Ÿ™‚

message on the storage manager / recovery guru : Logical Drive Not On Preferred Path