xjobs runs several jobs in parallel and limits the number of jobs running at once so that every processor of the machine is busy, but not overloaded. A batch of long-running processes invoked from the shell are normally executed one after another, no matter how many processors are available. xjobs allows batching those jobs while still keeping the machine busy. The interface of xjobs is similar to that of xargs.
| Tags | Utilities |
|---|---|
| Licenses | GPL |
| Operating Systems | POSIX Other Linux Solaris Unix |
Last announcement
Unfortunately, the xjobs-20100311 package ended up broken on the web server. I guess most people assumed that their problem extracting the archive ...
Recent releases


Release Notes: This release fixes a transient issue concerning job starting stalls on some systems when reading multiple scripts from a named pipe.


Release Notes: Removal of the DESTDIR install prefix was reverted. Some lint cleanups were made.


Release Notes: This release fixes resource usage display being omitted in certain cases, fixes weird time formatting, and has some minor cleanups.


Release Notes: This release adds the options -0 and -1 to simplify argument parsing based on newline and null character termination.


Release Notes: This is compatibility update for OpenBSD. It also adds support for job-specific work directories.
Recent comments
15 Sep 2010 22:32
This effect is due to argument parsing. This actually enables xjobs to pass more than one argument to every job, and even inconsistent number of arguments between jobs. So this is a feature not a bug. The latest release has a new options -1 and -0 that simplify the usage scenario you are complaining about.
07 Jun 2010 19:40
xjobs deals badly with special characters (such as space, ' and
"). To see the problem try this:
touch important_file
touch 'not important_file'
ls not* | xjobs rm
mkdir -p '12" records'
ls | xjobs rmdir
GNU Parallel www.gnu.org/software/p... does not suffer from this problem.