perl -pi -e ‘s/ORIG/NEW/g’

yum remove fuse fuse*
yum --enablerepo=base install yum-utils 
yumdownloader --enablerepo=base e2fsprogs-devel
rpm --nodeps -Uvh e2fsprogs-devel*.rpm
yum install gcc libstdc++-devel gcc-c++ curl curl* curl-devel libxml2 libxml2* libxml2-devel openssl-devel mailcap
cd /usr/local/src
wget --no-check-certificate "https://downloads.sourceforge.net/project/fuse/fuse-2.X/2.8.4/fuse-2.8.4.tar.gz?r=&ts=1312707573&use_mirror=kent"
tar -zxff fuse-2.8.4.tar.gz
cd fuse-2.8.4
./configure --prefix=/usr && make && make install
export PKG_CONFIG_PATH=/usr/lib/pkgconfig:/usr/lib64/pkgconfig/
ldconfig
modprobe fuse
pkg-config --modversion fuse (confirm correct version)
cd ../
wget http://s3fs.googlecode.com/files/s3fs-1.59.tar.gz
tar -zxf s3fs-1.59.tar.gz
cd s3fs-1.59
./configure --prefix=/usr && make && make install
vi /etc/passwd-s3fs (add aws id and secret key in format xxxxx:xxxxx)
mkdir /mnt/s3drive
s3fs bucket /mnt/s3drive

dump all running vms/data to the AWS S3 cloud mount (/mnt/s3drive)


deb http://backports.debian.org/debian-backports lenny-backports main
deb http://backports.debian.org/debian-backports lenny-backports-sloppy main


Install from the new target release:


apt-get install -t lenny-backports postgresql-common
apt-get install -t lenny-backports-sloppy postgresql-9.0 postgresql-client-9.0 postgresql-contrib-9.0


http://lists.debian.org/debian-backports-announce/2010/10/msg00000.html

cat dbname.pgdump | psql -d db_name

Or

psql -d db_name -f dbname.pgdump

Exporting a database from pgsql:

su – postgres
pg_dump dbname > dbname.pgdump

Exporting all databases from pgsql:

pg_dumpall -o > all_dbs.pgdump
psql -e template1 < all_dbs.pgdump

Check content field on records table for “.” entries. Once removed, the above error should go away.

This happens because the data directory structure has changed on MySQL 5.1 and you need to upgrade the directory structure for the affected database(s).

This is done by running the mysql_upgrade script which will examine all tables in all databases for incompatibilities with the current version of MySQL Server. It also upgrades the system tables so that you can take advantage of new privileges or capabilities that might have been added.

The mysql_upgrade script executes the following commands:

mysqlcheck --check-upgrade --all-databases --auto-repair
mysql_fix_privilege_tables
mysqlcheck --all-databases --check-upgrade --fix-db-names --fix-table-names

However, prior to MySQL 5.1.31, mysql_upgrade does not run the third command, which is necessary to re-encode database or table names that contain non-alphanumeric characters and remove the #mysql50# prefix. If you have such database or table names, execute the third command manually after executing mysql_upgrade or run the following query:

mysql > ALTER DATABASE `#mysql50#database` UPGRADE DATA DIRECTORY NAME;

http://dev.mysql.com/doc/refman/5.1/en/upgrading.html

https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2010-3301

Patch all 64-bit kernels

;; ANSWER SECTION:
incoming.mx. 86400 IN MX 10 mx.incoming.mx.

;; ADDITIONAL SECTION:
mx.incoming.mx. 86400 IN A 109.169.26.23

message_size_limit = 20480000

The above is roughly 20MB and is more than enough on a typical server.