diff options
-rw-r--r-- | NEWS | 21 | ||||
-rw-r--r-- | README | 31 |
2 files changed, 38 insertions, 14 deletions
@@ -1,2 +1,2 @@ -GNU Pies NEWS -- history of user-visible changes. 2016-02-24 +GNU Pies NEWS -- history of user-visible changes. 2016-03-15 Copyright (C) 2009-2016 Sergey Poznyakoff @@ -10,7 +10,22 @@ Version 1.2.93 (Git) +* SysV-style Init + +GNU Pies can now be used as init process daemon - the first process +started during booting. The configuration can be supplied both as +a traditional /etc/inittab file or as a native GNU Pies configuration +file. The control interface provides extensive monitoring and +management capabilities. + * Control interface -* SysV init support +The running GNU Pies instance can be queried and reconfigured on the +fly via a TCP socket (either UNIX or INET). Special utility, piesctl, +is included, which provides command line interface for inspecting +the state of components, reloading configuration (including addition +or removal of configuration files on the fly), stopping and restarting +components, etc. + +* Changes in configuration -* New flags +Two new flags are provided: @@ -1,3 +1,3 @@ GNU Pies README -Copyright (C) 2009-2013 Sergey Poznyakoff +Copyright (C) 2009-2016 Sergey Poznyakoff See the end of file for copying conditions. @@ -28,5 +28,11 @@ 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 @@ -35,11 +41,14 @@ 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. @@ -66,3 +75,3 @@ Send bug reports to <bug-pies@gnu.org.ua>. -Copyright (C) 2009-2013 Sergey Poznyakoff +Copyright (C) 2009-2016 Sergey Poznyakoff |