Free pipe fittings software for linux

Pipe Viewer project is a terminal-based tool for monitoring the progress of data through a pipeline.

It can be inserted into any normal pipeline between two processes to give a visual indication of how quickly data is passing through, how long it has taken, how near to completion it is, and an estimate of how long it will be until completion.

pv is now considered to be stable code: it appears to work reliably on systems it has been tested on.

Pipebench shows the current throughput and amount of data going through a pipe. It can be used to show the progress of a large md5sum process: cat bigfile | pipebench | md5sum.

Pipebench measures the speed of a pipe, by sitting in the middle passing the data along to the next process. Works on at least Linux, OpenBSD, NetBSD, Solaris and x86, Alpha, HPPA, Sparc and Sparc64.

Compiling

Just type make to compile.

Type make install to have pipebench be installed in /usr/local/bin

xmmspipe is a plugin for XMMS that enables it to be controlled by sending strings to a named pipe (FIFO). When you enable the plugin, XMMS can be commanded by sending strings to $HOME/.xmms/inpipe, for example,
echo play_pause > ~/.xmms/inpipe
will cause XMMS to pause or play.
Since version 0.5.0, it is possible to setup an output pipe, and query XMMS for information. For example, sending "report title" to the input pipe will cause the current songs title to be printed on the output pipe.
Included is a demo program called "fade", that shows how to use the plugin to fade the current song and advance to the next one. It requires the output pipe to be be enabled (via the Config window).
The Infopipe plugin does output pipes a little differently.
When I first wrote this plugin, I didnt know about other programs that I couldve used to control XMMS with shell scripts, such as xmmsctrl or xmms-shell. However, Ive kept xmmspipe alive because pipes may be preferable in some situations:
The pipe automatically inherits the security features of the underlying filesystem (e.g. you could change its permissions so that only users of a particular group can control XMMS).
In many programming languages, writing to a pipe is easier than executing programs, making it easier to build programs to control XMMS.
The plugin can call internal XMMS functions which means it can have more functionality than programs relying on the xmms_remote_* functions alone. For example, XMMSPipe can load/save playlists.
Sometimes I think XMMS itself should just be an MP3-playing daemon that interfaces with the outside world exclusively through pipes (one for input, at least one for output). This would allow a lot more flexibility, e.g. the GUI could be arbitrary and playlists could be managed by an external program. (It would work in the same way gkrellm works with files in /proc.) Also, the code would be simpler because it only has to worry about reading various audio formats and playing them. It wouldnt have to deal with window managers, X, etc.
Enhancements:
- Added playlist_move command due to Graeme Yeo

PAIP (pipe) is a universal filter application. It uses plugins to transmit and convert data. They can be nested, so the inner structures can become quite complex (non-linear). The command-line interface is similar to a programming language and very easy.
You will need:
gcc & GNU make
GNU sed
GNU install
libdl
libpthread
In three steps you can install it:
1) ./configure
Enter the destination path on prompt.
Just pressing will set the default path /usr/local.
2) make
3) make install
Enhancements:
- fixed Makefiles
- extended plugin socket (connections-switch)
- new using-plugin jpg2bmp
- new using-plugin gif2bmp

mod-auth-pipe is a module of authentication written for Apache 1 (it hasnt been tested with Apache 2, but it may work).

Actually, this module is just mod-auth-shadow with a few modifications in order to accept any program as a pipe, letting this one validate both users andr groups.

mod_auth_pipe contents the module itself and an example pipe.

mod-auth-pipe can be configured independantly for whole server, for any VirtualHost or just per Location/Directory. It has very few configuration variables and its format is very simple. In order to configure apache to authenticate, for example, access to the administrative interface of oscommerce you can type this on your httpd.conf:

< Directory /var/www/oscommerce/catalog/admin >
AuthType Basic
AuthName osCommerce admin site
AuthPipe on
AuthPipeProgram /usr/local/bin/auth-pipe
require group oscommerce-admins
< /Location >

This way, and with a well-made auth-pipe program you can be sure that only those within the group oscommerce-admins could enter that section of your web.

IO::Pipe::Producer is a Perl module that provides two modules getSubroutineProducer and getSystemProducer.

SYNOPSIS

# Module which provides 2 methods: getSubroutineProducer
# and getSystemProducer. They take a subroutine reference
# (with associated arguments) and a system call
# respectively and return (blessed) handles on their
# streaming standard output and standard error output.


# EXAMPLES of usage

use IO::Pipe::Producer;
$obj = new IO::Pipe::Producer();
$stdout_fh =
$obj->getSubroutineProducer($subroutine_reference,
@subroutine_parameters);

# OR

use IO::Pipe::Producer;
$obj = new IO::Pipe::Producer();
($stdout_fh,$stderr_fh) =
$obj->getSubroutineProducer($subroutine_reference,
@subroutine_parameters);

# OR

use IO::Pipe::Producer;
$stdout_fh = new IO::Pipe::Producer($subroutine_reference,
@subroutine_parameters);

# OR

use IO::Pipe::Producer;
($stdout_fh,$stderr_fh) =
new IO::Pipe::Producer($subroutine_reference,
@subroutine_parameters);

# Then you can read the returned handles like any other
# file handle...

while()
{print "STDOUT From Producer: $_"}
while()
{print "STDERR From Producer: $_"}

# You can also do the same thing with system calls using
# the getSystemProducer subroutine. However, this feature
# is not accessible via the new constructor

use IO::Pipe::Producer;
$obj = new IO::Pipe::Producer();
$stdout_fh =
$obj->getSystemProducer("echo "Hello World!"");

use IO::Pipe::Producer;
$obj = new IO::Pipe::Producer();
($stdout_fh,$stderr_fh) =
$obj->getSystemProducer("echo "Hello World!"");

# However, this is exactly the same as:

use IO::Pipe::Producer;
$stdout_fh = new Producer(sub{system(@_)},
"echo "Hello World!"");

# OR

use IO::Pipe::Producer;
($stdout_fh,$stderr_fh) =
new IO::Pipe::Producer(sub{system(@_)},
"echo "Hello World!"");

Bio::Tools::Run::PiseApplication::charge is a Perl module.

Bio::Tools::Run::PiseApplication::charge
Bioperl class for:

CHARGE Protein charge plot (EMBOSS)


Parameters:

(see also:
http://bioweb.pasteur.fr/seqanal/interfaces/charge.html
for available values):


charge (String)

init (String)

seqall (Sequence)
seqall -- protein [sequences] (-seqall)
pipe: seqsfile

window (Integer)
Window (-window)

aadata (String)
Amino acid property data file name (-aadata)

plot (Switch)
Produce graphic (-plot)

graph (Excl)
graph (-graph)

outfile (OutFile)
outfile (-outfile)

auto (String)

psouput (String)