developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
Changes since 1.0b4 [2004/08/07]:
- Use SHMUX_SPAWNMODE environmental variable, as per the manual page.
- New SHMUX_MAX environmental variable (suggested by Jon Amundsen).
Changes since 1.0b3 [2004/07/06]:
- ported to cygwin (problems reported by Jon Amundsen).
- better background detection code.
Changes since 0.13b [2004/06/07]:
- added code to try to avoid hanging accessing the controlling terminal.
- Sun's OpenSSH chokes on "-xa", use "-x -a" instead (reported by Poehner Uwe).
Changes since 0.12b [2004/04/05]:
- clear environment of harmful variables to run tests.
- updated "timers" test for Solaris.
- minor Makefile changes.
Changes since 0.11a [2003/11/28]:
- added test suite.
- fixed various minor problems with parsing of -A for regex/pcre analyzers.
- fixed fatal regex analyzer initialization problem.
- fixed mmap() usage.
Changes since 0.10a [2003/06/22]:
- suppressed extraneous empty lines in final report.
- fixed minor scheduling bug resulting in slower runs with the default "-S one".
- cleaned up handling of early termination.
- minor code cleanup in term.c.
- command timeouts (-C) are now also enforced by shmux with SIGTERM and SIGKILL.
Reset maintainer to tech-pkg on previous maintainers request.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
shmux is program for executing the same command on many hosts in parallel.
For each target, a child process is spawned by shmux, and a shell on
the target obtained one of the supported methods: rsh, ssh, or sh. The
output produced by the children is received by shmux and either output
in turn to the user, or written to files for later processing.
Submitted by Christophe Kalt <kalt@taranis.org> in PR 21961
