Some days ago I wrote a similar post about nagios and lighty, now I decided to test Icinga on Debian Squeeze.
The installation was pretty easy:
1 2 | aptitude install lighttpd aptitude install icinga |
To use Icinga we need following modules:
Linux TCP/IP, GreenIT and more…
Some days ago I wrote a similar post about nagios and lighty, now I decided to test Icinga on Debian Squeeze.
The installation was pretty easy:
1 2 | aptitude install lighttpd aptitude install icinga |
To use Icinga we need following modules:
The simple way to install grub/ grub2 from any linux live-CD or any other bootable medium.
Step 1: boot from linux live CD
Step 2: mount your hdd
Step 3: chroot in the mounted filesystem
Step 3: install grub
Step 4: reboot
1 2 3 4 5 6 | mount /dev/sda1 /mnt/ mount -t proc none /mnt/proc mount -o bind /dev /mnt/dev chroot /mnt/ /bin/bash /usr/sbin/grub-install --recheck --no-floppy /dev/sda reboot |
There are many configuration options with inpact on performance in Roundcube and behind it (Database and Webserver). As Roundcube installation administrator you can set them to some defaults and prevent users to change them by using the ‘dont_override‘ option.
I tested some options and created my tiny boost list.
Here’s the list of options with impact on performance
Messages listing is a main task of a mail client. Sorting is expensive. First of all you should use an IMAP server with SORT capability. If message list displaying is still too slow you should set ‘message_sort_col’ to an empty string.
‘message_sort_col’
Continue reading ‘Roundcube performance’
physical volumes:
o These are your physical disks, or disk partitions, such as /dev/hda or /dev/hdb1. These are what you’d be used to using when mounting/unmounting things. Using LVM we can combine multiple physical volumes into volume groups.
volume groups:
o A volume group is comprised of real physical volumes, and is the storage used to create logical volumes which you can create/resize/remove and use. You can consider a volume group as a “virtual partition” which is comprised of an arbitary number of physical volumes.
logical volumes:
o These are the volumes that you’ll ultimately end up mounting upon your system. They can be added, removed, and resized on the fly. Since these are contained in the volume groups they can be bigger than any single physical volume you might have. (ie. 4x5Gb drives can be combined into one 20Gb volume group, and you can then create two 10Gb logical volumes.)
1 | aptitude update && aptitude install lvm2 |
1 | pvcreate /dev/md0 |
Once we’ve initialised the partitions, or drives, we will create a volume group which is built up of them:
1 | vgcreate storm /dev/md0 |
If you’ve done this correctly you’ll be able to see it included in the output of:
1 | vgscan |
Create your first logical volume:
1 | lvcreate -n data --size 300g storm |
Your new logical volume will be accessible via:
1 2 3 | /dev/storm/data # or /dev/mapper/storm-data |
Create file system:
1 | mkfs.ext3 /dev/storm/data |
Show created volumes and their sizes:
1 | lvdisplay |
Extend volume:
1 | lvextend -L+10g /dev/storm/data |
After resizing you should resize the filesystem:
1 2 | e2fsck -f /dev/storm/data resize2fs /dev/storm/data |
Remove volume:
1 | lvremove /dev/storm/data |
If you need some visual help you can use: “system-config-lvm” utility co configure LVM.
root@web2:$ rm pe-warn-*.bz2
-bash: /bin/rm: Argument list too long
This peoblem happens when you are trying to delete too many files in a directory at the same time – it seems rm has special limits …
To solve the problem:
Use:
1 | find . -name 'pe-warn-*.bz2' | xargs rm |
or
1 | find . -name "pe-warn-*.bz2" -delete |