LadybirdBrowser/ladybird
1
1
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2024-09-21 10:19:03 +03:00
Code Issues Packages Projects Releases Wiki Activity

Base: Document new SystemServer abilities

Browse Source
This commit is contained in:
Sergey Bugaev 2020-06-09 00:03:12 +03:00 committed by Andreas Kling
parent 701994bfd1
commit f2d40ac2b2
Notes: sideshowbarker 2024-07-19 05:44:06 +09:00 
Author: https://github.com/bugaevc
Commit: https://github.com/SerenityOS/serenity/commit/f2d40ac2b28
Pull-request: https://github.com/SerenityOS/serenity/pull/2534
2 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Base/usr/share/man/man5/SystemServer.md
View File

@ -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

4
Base/usr/share/man/man7/SystemServer.md
View File

@ -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)