diff options
Diffstat (limited to 'README')
| -rw-r--r-- | README | 10 |
1 files changed, 5 insertions, 5 deletions
@@ -1,7 +1,7 @@ -Pies README +GNU Pies README Copyright (C) 2009 Sergey Poznyakoff See the end of file for copying conditions. * Introduction This file contains brief information about configuring, testing @@ -13,34 +13,34 @@ run `info -f doc/pies.info'. After the package is installed the documentation can be accessed running `info Pies'. Invoking `info pies' (with lower-case `p') will show you a concise description of the command line syntax (similar to a man-page style). * Overview -Pies (pronounced ``p-yes'') stands for the Program Invocation and +GNU Pies (pronounced ``p-yes'') stands for the Program Invocation and Execution Supervisor. This utility starts and controls execution of external programs, called ``components''. Each component is a stand-alone 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. -Pies supports a wide variety of component types. For example, it can +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 powerful access control lists, which are especially useful with such inetd-style components. -Pies can also be used to manage MeTA1 (http://meta1.org) 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. -Pies gives you complete control over the execution environment of +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. * Building |