Read Me

Compilation:

	make clean && make dep && make && make test


System-wide Installation:

	make install

then copy /etc/piper.conf.sample to /etc/piper.conf and edit it to cover
your needs.

Configuration file:

By default /etc/piper.conf is read, override with -c configfile option
A sample configuration file (piper.conf.sample):

Section test
  input		pipe reopen
  output	program

  logfile       piper.log
  pidfile       piper.pid

  ipipe		pipe
  opgm		OnTest
EndSection

Config file consist of sections. Defferent sections can be used for different
tasks to be done by a piper. The piper's -m <mode> is a task too do, e.g if
you use piper start -m test, then the "test"  config section is used.

Each section should contain:

input stdin|pipe|program
output stdout|pipe|program

If input is set to pipe then section should aslo contain:

ipipe filename

If input is set to program then section should aslo contain:

ipgm filename arg1 arg2 ...

For output use opipe and opgm

If input set to stdin or output set to stdout nothing else required

By default piper uses /var/log/piper/piper-<mode>.log for logging and
/var/run/piper/piper-<mode>.pid to store pid files. Directories
/var/run/piper and /var/log/piper are created if not exist. If piper can't
create those directories for some reason it will exit.

Logfile and Pidfile can be overriden in per-section basis by:

logfile filename
pidfile filename