From f2d40ac2b28b7919853b899c80877f7dc1bc8255 Mon Sep 17 00:00:00 2001 From: Sergey Bugaev Date: Tue, 9 Jun 2020 00:03:12 +0300 Subject: [PATCH] Base: Document new SystemServer abilities --- Base/usr/share/man/man5/SystemServer.md | 8 ++++++++ Base/usr/share/man/man7/SystemServer.md | 4 ++++ 2 files changed, 12 insertions(+) diff --git a/Base/usr/share/man/man5/SystemServer.md b/Base/usr/share/man/man5/SystemServer.md index a5cede161f..aff3c95ca8 100644 --- a/Base/usr/share/man/man5/SystemServer.md +++ b/Base/usr/share/man/man5/SystemServer.md @@ -28,6 +28,14 @@ describing how to launch and manage this service. * `WorkingDirectory` - the working directory in which the service is spawned. By default, services are spawned in the root (`"/"`) directory. * `BootModes` - a comma-separated list of boot modes the service should be enabled in. By default, services are only enabled in the "graphical" mode. The current boot mode is read from the kernel command line, and is assumed to be "graphical" if not specified there. * `Environment` - a space-separated list of "variable=value" pairs to set in the environment for the service. +* `MultiInstance` - whether multiple instances of the service can be running simultaneously. +* `AcceptSocketConnections` - whether SystemServer should accept connections on the socket, and spawn an instance of the service for each client connection. + +Note that: +* `Lazy` requires a `Socket`. +* `SocketPermissions` require a `Socket`. +* `MultiInstance` conflicts with `KeepAlive`. +* `AcceptSocketConnections` requires `Socket`, `Lazy`, and `MultiInstance`. ## Environment diff --git a/Base/usr/share/man/man7/SystemServer.md b/Base/usr/share/man/man7/SystemServer.md index 48dde03399..aaea86bd7c 100644 --- a/Base/usr/share/man/man7/SystemServer.md +++ b/Base/usr/share/man/man7/SystemServer.md @@ -42,6 +42,10 @@ configured to be *kept alive*, it can even exit after some period of inactivity; in this case SystemServer will respawn it again once there is a new connection to its socket. +SystemServer can also be configured to accept connections on the socket and +spawn separate instances of the service for each accepted connection, passing +the accepted socket to the service process. + ## See also * [`SystemServer`(5)](../man5/SystemServer.md)