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