aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--NEWS21
-rw-r--r--README31
2 files changed, 38 insertions, 14 deletions
diff --git a/NEWS b/NEWS
index b18fee2..d4e1d6e 100644
--- a/NEWS
+++ b/NEWS
@@ -1,21 +1,36 @@
1GNU Pies NEWS -- history of user-visible changes. 2016-02-24 1GNU Pies NEWS -- history of user-visible changes. 2016-03-15
2Copyright (C) 2009-2016 Sergey Poznyakoff 2Copyright (C) 2009-2016 Sergey Poznyakoff
3See the end of file for copying conditions. 3See the end of file for copying conditions.
4 4
5Please send Pies bug reports to <bug-pies@gnu.org> or 5Please send Pies bug reports to <bug-pies@gnu.org> or
6<bug-pies@gnu.org.ua> 6<bug-pies@gnu.org.ua>
7 7
8 8
9Version 1.2.93 (Git) 9Version 1.2.93 (Git)
10 10
11* SysV-style Init
12
13GNU Pies can now be used as init process daemon - the first process
14started during booting. The configuration can be supplied both as
15a traditional /etc/inittab file or as a native GNU Pies configuration
16file. The control interface provides extensive monitoring and
17management capabilities.
18
11* Control interface 19* Control interface
12 20
13* SysV init support 21The running GNU Pies instance can be queried and reconfigured on the
22fly via a TCP socket (either UNIX or INET). Special utility, piesctl,
23is included, which provides command line interface for inspecting
24the state of components, reloading configuration (including addition
25or removal of configuration files on the fly), stopping and restarting
26components, etc.
27
28* Changes in configuration
14 29
15* New flags 30Two new flags are provided:
16 31
17- siggroup 32- siggroup
18 33
19This flag instructs pies to send termination signal to the process 34This flag instructs pies to send termination signal to the process
20group of the process being stopped. 35group of the process being stopped.
21 36
diff --git a/README b/README
index ee8e3d7..0b23ebe 100644
--- a/README
+++ b/README
@@ -1,8 +1,8 @@
1GNU Pies README 1GNU Pies README
2Copyright (C) 2009-2013 Sergey Poznyakoff 2Copyright (C) 2009-2016 Sergey Poznyakoff
3See the end of file for copying conditions. 3See the end of file for copying conditions.
4 4
5* Introduction 5* Introduction
6 6
7This file contains brief information about configuring, testing 7This file contains brief information about configuring, testing
8and running Pies. It is *not* intended as a replacement 8and running Pies. It is *not* intended as a replacement
@@ -23,28 +23,37 @@ program, designed to be executed in the foreground. Upon startup pies
23reads the list of components from its configuration file, starts them, 23reads the list of components from its configuration file, starts them,
24and remains in the background, controlling their execution. When a 24and remains in the background, controlling their execution. When a
25component terminates, pies tries to restarts it. Its configuration allows 25component terminates, pies tries to restarts it. Its configuration allows
26to specify actions other than simple restart, depending on the exit code 26to specify actions other than simple restart, depending on the exit code
27of the component. 27of the component.
28 28
29GNU Pies gives you complete control over the execution environment of
30each component. This includes modifying shell environment, running
31components with the given user privileges, etc. The standard error
32and/or output of any component may be redirected either to a disk
33file or to syslog.
34
29GNU Pies supports a wide variety of component types. For example, it can 35GNU Pies supports a wide variety of component types. For example, it can
30bind the standard input and output of a component to a network socket, 36bind the standard input and output of a component to a network socket,
31which makes pies a replacement for the inetd utility. Pies implements 37which makes pies a replacement for the inetd utility. Pies implements
32powerful access control lists, which are especially useful with such 38powerful access control lists, which are especially useful with such
33inetd-style components. 39inetd-style components.
34 40
35GNU Pies can also be used to manage MeTA1 (http://meta1.org) components. 41GNU Pies can also be used to manage MeTA1 (http://meta1.org) components.
36Moreover, it is able to use MeTA1 configuration file directly, so that
37migration from the native mcp utility to pies does not require any
38efforts.
39 42
40GNU Pies gives you complete control over the execution environment of 43To facilitate its use, GNU Pies is able to parse configuration files
41each component. This includes modifying shell environment, running 44in various formats, such as traditional inetd.conf, or meta1.conf. So
42components with the given user privileges, etc. The standard error 45that, e.g. migration from the native mcp utility to pies does not
43and/or output of any component may be redirected either to a disk 46require any efforts.
44file or to syslog. 47
48Finally, GNU Pies can be used as init process - the first process
49started during booting. In this case, the configuration can be
50supplied both in the traditional inittab or in native Pies formats.
51
52The running GNU Pies instance can be queried and reconfigured on the
53fly via a TCP socket.
45 54
46* Building 55* Building
47 56
48A usual three-state procedure: 57A usual three-state procedure:
49 58
50 ./configure 59 ./configure
@@ -61,13 +70,13 @@ Please, see the Pies documentation.
61 70
62Send bug reports to <bug-pies@gnu.org.ua>. 71Send bug reports to <bug-pies@gnu.org.ua>.
63 72
64 73
65* Copyright information: 74* Copyright information:
66 75
67Copyright (C) 2009-2013 Sergey Poznyakoff 76Copyright (C) 2009-2016 Sergey Poznyakoff
68 77
69 Permission is granted to anyone to make or distribute verbatim copies 78 Permission is granted to anyone to make or distribute verbatim copies
70 of this document as received, in any medium, provided that the 79 of this document as received, in any medium, provided that the
71 copyright notice and this permission notice are preserved, 80 copyright notice and this permission notice are preserved,
72 thus giving the recipient permission to redistribute in turn. 81 thus giving the recipient permission to redistribute in turn.
73 82

Return to:

Send suggestions and report system problems to the System administrator.