aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorSergey Poznyakoff <gray@gnu.org.ua>2016-03-15 13:40:03 +0200
committerSergey Poznyakoff <gray@gnu.org.ua>2016-03-15 13:40:44 +0200
commit174b7f83934eecb2bbb0502e6645f55872d3e783 (patch)
tree6b8dd6aee542ade2a5333fcd60d74b0c1412e968 /README
parented7aa572e52a3dec942c348face2487f71297086 (diff)
downloadpies-174b7f83934eecb2bbb0502e6645f55872d3e783.tar.gz
pies-174b7f83934eecb2bbb0502e6645f55872d3e783.tar.bz2
Update NEWS and README
Diffstat (limited to 'README')
-rw-r--r--README31
1 files changed, 20 insertions, 11 deletions
diff --git a/README b/README
index ee8e3d7..0b23ebe 100644
--- a/README
+++ b/README
@@ -1,8 +1,8 @@
GNU Pies README
-Copyright (C) 2009-2013 Sergey Poznyakoff
+Copyright (C) 2009-2016 Sergey Poznyakoff
See the end of file for copying conditions.
* Introduction
This file contains brief information about configuring, testing
and running Pies. It is *not* intended as a replacement
@@ -23,28 +23,37 @@ program, designed to be executed in the foreground. Upon startup pies
reads the list of components from its configuration file, starts them,
and remains in the background, controlling their execution. When a
component terminates, pies tries to restarts it. Its configuration allows
to specify actions other than simple restart, depending on the exit code
of the component.
+GNU Pies gives you complete control over the execution environment of
+each component. This includes modifying shell environment, running
+components with the given user privileges, etc. The standard error
+and/or output of any component may be redirected either to a disk
+file or to syslog.
+
GNU Pies supports a wide variety of component types. For example, it can
bind the standard input and output of a component to a network socket,
-which makes pies a replacement for the inetd utility. Pies implements
+which makes pies a replacement for the inetd utility. Pies implements
powerful access control lists, which are especially useful with such
inetd-style components.
GNU Pies can also be used to manage MeTA1 (http://meta1.org) components.
-Moreover, it is able to use MeTA1 configuration file directly, so that
-migration from the native mcp utility to pies does not require any
-efforts.
-GNU Pies gives you complete control over the execution environment of
-each component. This includes modifying shell environment, running
-components with the given user privileges, etc. The standard error
-and/or output of any component may be redirected either to a disk
-file or to syslog.
+To facilitate its use, GNU Pies is able to parse configuration files
+in various formats, such as traditional inetd.conf, or meta1.conf. So
+that, e.g. migration from the native mcp utility to pies does not
+require any efforts.
+
+Finally, GNU Pies can be used as init process - the first process
+started during booting. In this case, the configuration can be
+supplied both in the traditional inittab or in native Pies formats.
+
+The running GNU Pies instance can be queried and reconfigured on the
+fly via a TCP socket.
* Building
A usual three-state procedure:
./configure
@@ -61,13 +70,13 @@ Please, see the Pies documentation.
Send bug reports to <bug-pies@gnu.org.ua>.
* Copyright information:
-Copyright (C) 2009-2013 Sergey Poznyakoff
+Copyright (C) 2009-2016 Sergey Poznyakoff
Permission is granted to anyone to make or distribute verbatim copies
of this document as received, in any medium, provided that the
copyright notice and this permission notice are preserved,
thus giving the recipient permission to redistribute in turn.

Return to:

Send suggestions and report system problems to the System administrator.