Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
This branch is 306 commits ahead of SpamapS:master.

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time
November 18, 2023 14:47
December 10, 2017 22:32
November 3, 2023 13:34
October 18, 2012 23:14
September 8, 2020 14:54
February 9, 2014 04:30
September 15, 2008 19:17


Build Status

The latest version of gearmand source code and versions 1.1.13 and later can be found at GitHub Repository. Older versions released before 1.1.13 can be found at Launchpad Repository.

You can grab the latest release distribution of Gearman from Unless otherwise specified, releases are GPG-signed by Clint Byrum, whose public key can be found at

What Is Gearman?

Gearman provides a generic application framework to farm out work to other machines or processes that are better suited to do the work. It allows you to do work in parallel, to load balance processing, and to call functions between languages. Gearman is the nervous system for how distributed processing communicates.

If you downloaded this package as a tar.gz distribution, you'll want to read Getting Started section below or visit the more detailed web page Getting Started

If you are interested in developing or submitting patches to the project, read the Contributing section below and check out the file for Coding Style and COPYING for details on licensing.

Getting Started

If you want to work on the latest code, please read the file

To build a release version from a tarball (.tar.gz or .tgz), you can follow the normal:

Change into the directory where you saved the tarball and run:

tar xzf gearmand-X.Y.tar.gz
cd gearmand-X.Y

Then run the usual autoconfigure style build (you may need to use sudo to install):

make install

There are various dependencies that may be satisfied on Ubuntu by installing these packages:

sudo apt install automake autoconf libtool make curl gcc g++ git gperf     \ 
    libssl-dev libboost-all-dev libevent-dev libhiredis-dev libpq-dev      \ 
    libtokyocabinet-dev python3-sphinx uuid-dev

You can also run make test before installing to make sure everything checks out ok. You can also streamline the process of building and testing by running:

./configure && make && make test
make install

Once you have it installed, you can start the Gearman job server with:

gearmand --verbose INFO

This will start it while printing some verbose messages. To try running a job through it, look in the examples/ directory of this source and run:


Once that is running, you can run your first job with:

./reverse_client "Hello, Gearman!"

If all goes well, the reverse_worker application should have output:

Job=H:lap:1 Workload=Hello, Gearman! Result=!namraeG ,olleH

While the reverse_client returned:

Result=!namraeG ,olleH

There are a lot more details about gearmand at Getting Started.

If you want to start writing your own client and workers, be sure to check out the Developer API documentation.

There are also many other Useful Resources to help you put gearmand to work for you!



The current versions of geamand are maintained on our GitHub Repo for gearmand.

If you are not familiar with git, you can find more info at Getting Started with Git.

Please follow these instructions to clone, create a branch, and generate a pull request on that branch. More details on using GitHub can be found at GitHub Help.

  1. Clone the GitHub repository to your local file system:

     git clone

    If you do not have access to create branches in the gearmand GitHub repository, you should fork the repository and clone your fork instead. Refer to Contributing to Open Source on GitHub for details.

  2. Next, think of a clear, descriptive branch name and then create a new branch and change to it:

     cd gearmand
     git checkout -b DESCRIPTIVE_BRANCH_NAME
  3. Once the tree is branched you will need to generate the "configure" script for autoconfigure.

     ./ -a
  4. Finally, you are ready to run tests, make changes to the code, commit and push them to GitHub, and generate a pull request on your branch so we can consider your changes.

You can learn more about how to Create a Pull Request and Create a Pull Request from a Fork.

But Wait! There's More!

Once you have made your changes there are two additional make targets to build release ready distributions:

To generate a tarball distribution of your code:

make dist

Or to generate an RPM distribution use:

make rpm

Thanks and keep hacking!

Seattle, WA.


No packages published


  • C++ 72.3%
  • C 16.2%
  • M4 9.2%
  • Shell 1.4%
  • Dockerfile 0.5%
  • Makefile 0.4%