How 2 #CentOS A Centos Installation Repository

28Feb/100

Fight Spam With #ASSP (Anti-Spam SMTP Proxy) On CentOS 5.4

  • Stumbleupon
  • Google Buzz

The Anti-Spam SMTP Proxy (ASSP) server project is an Open Source, Perl based, platform-independent transparent SMTP proxy server that leverages numerous methodologies and technologies to both rigidly and adaptively identify e-mail spam. ASSP is easy to set up because it requires only minor changes to the configuration of your your Mail Transfer Agent.

Also please read the ASSP documentation

Preliminary Note

In this tutorial I use a base 32 bit server install with the hostname server1.example.co.za with the IP address 10.0.0.10. These settings might differ for you, so you have to replace them where appropriate.

Adjust any package names if installing the EL4 or 64 bit packages. If any dependencies are unsatisfied, install the required packages and retry

15Feb/100

#Subversion: Failed to get lock on destination repository

  • Stumbleupon
  • Google Buzz

In the event that your Subversion server was powered down incorrectly during one of its subversion mirror synchronizations you might end up with a lock on the destination repository. This basic tutorial will help you to remove the lock and continue with your synchronizations.

Below is the output from the svnsync showed this:

# /usr/bin/svnsync --non-interactive synchronize svn://{destination repository}/opt/svn/{repo}

Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
svnsync: Couldn't get lock on destination repos after 10 attempts

To remove the lock you'll need to do the following:

# svn propdel svn:sync-lock --revprop -r 0 svn://{destination repository}/opt/svn/{repo}
# /usr/bin/svnsync --non-interactive synchronize svn://{destination repository}/opt/svn/{repo}

Committed revision 1694.
Copied properties for revision 1694.
Committed revision 1695.
Copied properties for revision 1695.

Tagged as: No Comments
31Jan/100

#Firewall Migration and Planning Guide

  • Stumbleupon
  • Google Buzz

firewallPlan and document existing firewall
Planning and documenting the migration of the firewall is critical, without it you're doomed. Over time configurations grow as rules and networks are added for specific purposes are often superseded or simply forgotten.

You need to document these as well as any other additional services or features (i.e. DHCP, DNS or VPN). This will assist you while you recreate the policies behind the firewall rules.

You can download a sample Firewall Planning Guide here:

Firewall Planning Guide (65)
8Dec/0910

Creating a Local #Fedora 12 #Yum Repository

  • Stumbleupon
  • Google Buzz

yumfedora Fedora 12 has just been released so it's time to add it to our arsenal of local yum repositories. We all know the importance of creating a local YUM repository on your LAN. Not only do you decrease the time it takes to download and install updates, you also decrease bandwidth usage.

This How To will show you a simple yet effective way of setting up your local Fedora 12 YUM repository and client.

TIP: Distribute your Fedora YUM configuration via your Puppet Master