Skip to content

Commit

Permalink
doc: add README note about supplementary groups
Browse files Browse the repository at this point in the history
  • Loading branch information
gmcn42 committed Feb 19, 2025
1 parent 5f1bbfa commit d935213
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -236,8 +236,8 @@ IO_REDIRECT = STDERR STDOUT
- **STOP_COMMAND** -- Optional. Given commands are executed on `crinit-ctl stop <TASKNAME>`, `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 `<taskname>:{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
Expand Down

0 comments on commit d935213

Please sign in to comment.