forked from lix-project/lix
f7ab93b068
after discussing this with multiple people, I'm convinced that "build task" is more precise: a derivation is not an action, but inert until it is built. also it's easier to pronounce. proposal: use "build task" for the generic concept "description of how to derive new files from the contents of existing files". then it will be easier to distinguish what we mean by "derivation" (a specific data structure and Nix language value type) and "store derivation" (a serialisation of a derivation into a file in the Nix store).
22 lines
468 B
Markdown
22 lines
468 B
Markdown
R""(
|
|
|
|
# Example
|
|
|
|
* Run the daemon in the foreground:
|
|
|
|
```console
|
|
# nix daemon
|
|
```
|
|
|
|
# Description
|
|
|
|
This command runs the Nix daemon, which is a required component in
|
|
multi-user Nix installations. It runs build tasks and other
|
|
operations on the Nix store on behalf of non-root users. Usually you
|
|
don't run the daemon directly; instead it's managed by a service
|
|
management framework such as `systemd`.
|
|
|
|
Note that this daemon does not fork into the background.
|
|
|
|
)""
|