BSD Ports

sysutils/parafly 0.1.0_9,1 FreeBSD

Process multiple commands in parallel on a single server

System
FreeBSD
Repository
FreeBSD ports
Maintainer
[email protected]
Last update
Commit
2414383046
License
BSD3CLAUSE
Categories
sysutils
Package size
15.4 KiB, 36.5 KiB installed

Description

Given a file containing a list of Unix commands, multithreading is used to process the commands in parallel on a single server. Success/failure is captured, and failed commands are retained and reported.

In the other systems

SystemPortVersion
FreeBSDsysutils/parafly0.1.0_9,1
DragonFlysysutils/parafly0.1.0_9,1

Install

Binary package:

pkg install parafly

From the ports tree:

cd /usr/ports/sysutils/parafly/ && make install clean

To depend on this port in another port's Makefile:

RUN_DEPENDS=	parafly>0:sysutils/parafly

Packages

The version each package repository carries. “-” means the repository builds no package of it, “n/a” that there is no such repository.

Repositoryaarch64amd64armv6armv7i386
FreeBSD:14:latest0.1.0_9,10.1.0_9,1-0.1.0_9,10.1.0_9,1
FreeBSD:14:quarterly0.1.0_9,10.1.0_9,1n/a0.1.0_9,10.1.0_9,1
FreeBSD:15:latest0.1.0_9,10.1.0_9,1n/a0.1.0_9,10.1.0_9,1
FreeBSD:15:quarterly0.1.0_9,10.1.0_9,1n/an/an/a
FreeBSD:16:latest0.1.0_9,10.1.0_9,1n/an/an/a
FreeBSD:16:quarterlyn/an/an/an/an/a

Dependencies

The Makefile names none itself; they come from USES and USE_*.

The full lists below include those, and their dependencies in turn.

No port depends on this one.

Configuration

No options to configure.

Service scripts
none

Files

distinfo 1
FileSizeSHA256
parafly-ParaFly-v0.1.0_GH0.tar.gz233214662e8bc2d7f5dae2cb63804bba13b4790eeda9f4e40126e1d947005c89134c4d

Commit history 1

DateCommitCreditsLog message
2414383046 Jason W. Bacon Release numerous ports to ports@
I've been retired for a few years, and it is unlikely I will be doing any more scientific computing support in the future. I have continued to maintain ~160 ports to the best of my ability, mainly as a favor to the community, but I can no longer justify the time and effort required. I am therefore releasing most of my scientific ports, along with a few others, to ports@. I will continue to maintain ports I am actively using and those for which I am upstream.