From d935213e5ba7e9699bc4e8666eb9b69c8fbc52d4 Mon Sep 17 00:00:00 2001 From: Andreas Zdziarstek Date: Wed, 19 Feb 2025 17:40:32 +0100 Subject: [PATCH] doc: add README note about supplementary groups --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ec7d98e..d5e95e9 100644 --- a/README.md +++ b/README.md @@ -236,8 +236,8 @@ IO_REDIRECT = STDERR STDOUT - **STOP_COMMAND** -- Optional. Given commands are executed on `crinit-ctl stop `, `crinit-ctl poweroff` or `crinit-ctl reboot` instead of sending the regular `SIGTERM`. Same rules as for **COMMAND** apply. Additionally the variable "TASK_PID" can be used and will be expanded with the stored PID of the task. Example: `STOP_COMMAND = /usr/bin/kill ${TASK_PID}`. Please note that TASK_PID will expand to "-1" if the task is no longer running or has forked itself without notifying Crinit. **ATTENTION:** Currently STOP_COMMAND does not support IO_REDIRECT! Its output will not be redirected! - **USER** -- Name of the user used to run the commands specified in **COMMAND**. Either the username or the numeric user ID can be used. If **USER** is not set, "root" is assumed. **NOTE**: Changing user names, UIDs, group names or GIDs on the system while a task using them has already been loaded may result in undefined behaviour. -- **GROUP** -- Name of the group used to run the commands specified in **COMMAND**. Either the group name or the numeric group ID can be used. If **GROUP** is not set, "root" is assumed. -**See note on USER command.** This applies here, too. +- **GROUP** -- Name of the group used to run the commands specified in **COMMAND**. Either the group name or the numeric group ID can be used. If **GROUP** is not set, "root" is assumed. Note that setting supplementary groups is not yet supported. +**Also see note on USER command.** This applies here, too. - **DEPENDS** -- A list of dependencies which need to be fulfilled before this task is considered "ready-to-start". Semantics are `:{fail,wait,spawn}`, where `spawn` is fulfilled when (the first command of) a task has been started, `wait` if it has successfully completed, and `fail` if it has failed somewhere along the way. Here we can see