Differences between revisions 3 and 4
Revision 3 as of 2007-09-25 21:40:21
Size: 1417
Editor: JustinMason
Comment: add make test as a requirement
Revision 4 as of 2009-09-20 23:16:22
Size: 1417
Editor: localhost
Comment: converted to 1.6 markup
No differences found!

The nightly mass-check setup on the SpamAssassin zone, spamassassin.zones.apache.org, uses helper "slaves" to actually scan the mail in order to reduce CPU load.

Setup

Here's how to set up a new slave.

  • Install perl, and all of SpamAssassin's required modules, and whatever modules are required for "mass-check" (see MassCheck) to operate.

  • make sure SpamAssassin's "make test" of current SVN trunk passes.

  • Create a user called "mccli". It does not need a password. This is the user the mass-checks will run as.
  • Generate an SSH key for that user:

  sudo -u mccli -H bash
  ssh-keygen -t rsa
  • Add the master server's SSH key to '~/.ssh/authorized_keys':

  curl http://bbmass.spamassassin.org/pubkey.txt > ~/.ssh/authorized_keys
  chmod 600 ~/.ssh/authorized_keys
  • Ensure the new slave's SSH server is accessible to the net, and allows logins as "mccli".
  • on the Zone, test it:

  sudo -u bbmass -H ssh mccli@hostname.domain.com echo tst

You will be prompted to accept a new host fingerprint; you should then see the string "tst".

Once this works, edit trunk/build/nightlymc/clienthosts in SVN, and add the login username@host to the list:

mccli@host.domain.org
mccli@another.domain2.org

The new mass-check client should be used in the next nightly mass-check (depending on when the "nightly" tag is applied).

MassCheckSlave (last edited 2009-09-20 23:16:22 by localhost)