If you are trying to compile dovecot against PostgreSQL, then you are probably running configure with the "--with-pgsql" option. Except that if you installed PostgreSQL via the PGDG repository on Centos 6, you are probably stuck with the following error:
checking for shadow.h... yes
checking for pam_start in -lpam... no
checking for auth_userokay... no
checking for pg_config... NO
checking for PQconnectdb in -lpq... no
configure: error: Can't build with PostgreSQL support: libpq not found
The root cause is that pg_config is not in the PATH statement. So you should add "/usr/pgsql-9.2/bin" to your PATH statement before calling ./configure. If you are not sure where pg_config is located, try "find / -name pg_config".
#!/bin/bash
PATH=/usr/pgsql-9.2/bin:$PATH
export PATH
./configure \
--with-pgsql
Once you do the above, the dovecot 2.2 configure script will run to completion.
Wednesday, May 29, 2013
Saturday, May 18, 2013
FSVS automated snapshots
One common use for FSVS is to make automated snapshots of portions of your Linux file system. Such as monitoring changes to log files, executables, or data directories. The downside of this is that, even if nothing as changed, FSVS will still generate a SVN commit. So if you are running FSVS on an hourly basis through the day, your SVN log will be cluttered with hundreds of commits that contain no useful information.
The following is an example of how we keep track of changes to a /cfmc directory on the server. This runs hourly and is our primary backup against data loss on this server. Because FSVS and SVN only send the differences across the wire, it's a very efficient method. And since this is protecting client data, we're going to version control it and keep it for years.
The magic trick is the FCOUNT= line which runs FSVS and looks to see whether there were any changes to files in the monitored directory tree. If it found changes, then we go ahead and do an automated commit.
The following is an example of how we keep track of changes to a /cfmc directory on the server. This runs hourly and is our primary backup against data loss on this server. Because FSVS and SVN only send the differences across the wire, it's a very efficient method. And since this is protecting client data, we're going to version control it and keep it for years.
The magic trick is the FCOUNT= line which runs FSVS and looks to see whether there were any changes to files in the monitored directory tree. If it found changes, then we go ahead and do an automated commit.
#!/bin/sh # Only executes FSVS if FSVS reports outstanding changes FSVS_CONF=~/.fsvs-conf FSVS_WAA=~/.fsvs-waa export FSVS_CONF FSVS_WAA cd /cfmc FCOUNT=`/usr/local/bin/fsvs | grep -v 'dir.*\.$' | wc -l` if [ $FCOUNT -gt 0 ] ; then /usr/local/bin/fsvs ci -m "Automatic FSVS snapshot" else echo "Nothing changed" fi
Subscribe to:
Posts (Atom)