Home
last modified time | relevance | path

Searched refs:environment (Results 1 – 25 of 101) sorted by relevance

12345

/systemd-251/test/units/
Dtestsuite-26.sh7 systemctl show-environment | grep -q '^PATH='
10 systemctl set-environment PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/testaddition FOO=…
13 systemctl show-environment | grep -q '^PATH=.*testaddition$'
14 systemctl show-environment | grep -q '^FOO=BAR$'
19 systemctl show-environment | grep -q '^PATH=.*testaddition$'
20 systemctl show-environment | grep -q '^FOO=BAR$'
23 systemctl show-environment --output=json | grep -q '^{.*"FOO":"BAR".*}$'
26 systemctl unset-environment FOO PATH
29 systemctl show-environment | grep '^FOO=$' && exit 1
30 systemctl show-environment | grep '^PATH=.*testaddition$' && exit 1
[all …]
/systemd-251/src/core/
Dlocale-setup.c16 int locale_setup(char ***environment) { in locale_setup() argument
82 if (strv_isempty(*environment)) in locale_setup()
83 strv_free_and_replace(*environment, add); in locale_setup()
87 merged = strv_env_merge(*environment, add); in locale_setup()
91 strv_free_and_replace(*environment, merged); in locale_setup()
Dlocale-setup.h4 int locale_setup(char ***environment);
Dexecute.h177 char **environment; member
395 char **environment; member
/systemd-251/shell-completion/zsh/
D_systemctl.in71 "show-environment:Dump environment"
72 "set-environment:Set one or more environment variables"
73 "unset-environment:Unset one or more environment variables"
74 "import-environment:Import environment variables set on the client"
104 local -a groups=( unit machine unit_file job environment manager_state system )
357 for fun in set-environment unset-environment ; do
362 if [[ "${fun}" = "set-environment" ]]; then
365 _wanted systemd-environment expl 'environment variable' \
366 compadd "$@" ${suf} - ${${(f)"$(systemctl show-environment)"}%%=*}
370 (( $+functions[_systemctl_import-environment] )) || _systemctl_import-environment()
[all …]
D_hostnamectl35 _message "new environment"
58 "deployment:Get/set deployment environment for host"
D_systemd-nspawn45 …ecifies an environment variable assignment to pass to the init process in the container, in the fo…
/systemd-251/xorg/
D50-systemd-user.sh11 systemctl --user import-environment DISPLAY XAUTHORITY
13 if command -v dbus-update-activation-environment >/dev/null 2>&1; then
14 dbus-update-activation-environment DISPLAY XAUTHORITY
/systemd-251/shell-completion/bash/
Dsystemctl.in212 [ENVS]='set-environment unset-environment import-environment'
217 reboot rescue show-environment suspend get-default
328 elif [ "$verb" = 'unset-environment' ]; then
329 comps=$( __systemctl $mode show-environment \
333 elif [ "$verb" = 'set-environment' ]; then
334 comps=$( __systemctl $mode show-environment \
338 elif [ "$verb" = 'import-environment' ]; then
/systemd-251/docs/
DCREDENTIALS.md19 environment variables (which is problematic because by default they are
30 path to access them is derived from the environment variable
34 environment variables the credential data is not propagated down the process
55 environment and the EFI System Partition (via `systemd-stub`). Such system
107 environment variable `$CREDENTIALS_DIRECTORY` set. It contains an absolute path
110 `$CREDENTIALS_DIRECTORY` environment variable passed to the service processes
138 the path to it as environment variable `$FOOBARPATH` the credential is also
139 accessible as the path in that environment variable. When invoked, the service
149 supplied as environment variable, use the `%d` specifier in the `Environment=`
248 1. A container manager may set the `$CREDENTIALS_DIRECTORY` environment
[all …]
DENVIRONMENT.md11 environment variables. Many of these environment variables are not supported at
17 Below is an (incomprehensive) list of the environment variables understood by
18 the various tools. Note that this list only covers environment variables not
27 even if a `chroot()` environment is detected. You almost certainly want to
32 `chroot()` environment. This is particularly relevant for systemctl, as it
100 method" is used, but this can be overridden with this environment variable.
209 naming across updates. This environment variable takes precedence over the
232 first existing unit listed in the environment variable, and
252 done when this environment variable is used.
265 setting environment variables is of course possible in any even unprivileged
[all …]
DCONTAINER_INTERFACE.md97 a container, please set the `$container` environment variable for PID 1 in
105 container. The container manager should set `$container_uuid` as environment
117 manager can set the `$container_ttys` environment variable for the
133 environment variable for the ID fields described by the [os-release
146 `$CREDENTIALS_DIRECTORY` environment variable. If the container managers
195 set the `$NOTIFY_SOCKET` environment variable to a suitable socket path to
253 matter much as it is communicated via the `$NOTIFY_SOCKET` environment
259 information about the host environment, on top of what `uname -a` reports.
262 information as the `$container` environment variable (see above), i.e. a
266 unprivileged without access to the container PID 1's environment block.
[all …]
DDESKTOP_ENVIRONMENTS.md23 to the existing session, allowing the graphical environment to present it
76 adjusted using desktop environment specific drop-in files.
101 `X-KDE-autostart-condition=` and `AutostartCondition=` by using desktop-environment-provided
DJOURNAL_NATIVE_PROTOCOL.md57 Each datagram should consist of a number of environment-like key/value
58 assignments. Unlike environment variable assignments the value may contain NUL
168 environment variable. The systemd service logic sets this variable to a
176 Why bother with this environment variable check? A service program invoked by
DTESTING_WITH_SANITIZERS.md25 sanitizers; e.g. in systemd we set the following environment variables:
46 to the `meson` call and use the same environment variables for runtime configuration.
DPORTABLE_SERVICES.md58 "Portable services" do not provide a fully isolated environment to the payload,
63 code in a different, isolated environment from the host — like most containers
64 would — but to run it in the same environment, but with stricter access
70 supposed to manage anything in their own environment (such as the network) as
71 the execution environment is mostly shared with the rest of the system.
298 services. Hence there's no new execution environment to consider. And, unlike
/systemd-251/src/systemctl/
Dmeson.build56 'systemctl-set-environment.c',
57 'systemctl-set-environment.h',
/systemd-251/test/test-execute/
Dexec-passenvironment-absent.service3 Description=Test for PassEnvironment with variables absent from the execution environment
/systemd-251/src/shared/
Dserialize.h25 int deserialize_environment(const char *value, char ***environment);
Duser-record-show.c242 if (!strv_isempty(hr->environment)) in user_record_show()
243 STRV_FOREACH(i, hr->environment) { in user_record_show()
244 printf(i == hr->environment ? in user_record_show()
/systemd-251/man/rules/
Dmeson.build19 ['environment.d', '5', [], 'ENABLE_ENVIRONMENT_D'],
877 ['systemd-environment-d-generator',
879 ['30-systemd-environment-d-generator'],
1057 ['systemd.environment-generator', '7', [], 'ENABLE_ENVIRONMENT_D'],
/systemd-251/units/
Dconsole-getty.service.in24 # option to preserve environment (-p), followed by '--' for safety, and then
Dcontainer-getty@.service.in29 # option to preserve environment (-p), followed by '--' for safety, and then
Dsystemd-boot-system-token.service18 # Don't run this in a VM environment, because there EFI variables are not
/systemd-251/.github/workflows/
Dcoverity.yml29 …-team@latest/actions/reference/workflow-commands-for-github-actions#setting-an-environment-variable

12345