| /systemd-251/shell-completion/bash/ |
| D | systemd-run | 37 --on-active --on-boot --on-startup --on-unit-active --on-unit-inactive --on-calendar
38 --on-clock-change --on-timezone-change --path-property --socket-property
46 … -E --setenv --on-active --on-boot --on-startup --on-unit-active --on-unit-inactive --on-calendar
62 …--unit|--description|--on-active|--on-boot|--on-startup|--on-unit-active|--on-unit-inactive|--on-c…
|
| /systemd-251/shell-completion/zsh/ |
| D | _systemd-run | 30 {-H+,--host=}'[Operate on remote host]:[user@]host:_sd_hosts_or_user_at_host' \
31 {-M+,--machine=}'[Operate on local container]:machines:_sd_machines' \
35 '--on-active=[Run after SEC seconds]:SEC' \
36 '--on-boot=[Run SEC seconds after machine was booted up]:SEC' \
37 '--on-calendar=[Realtime timer]:SPEC' \
38 '--on-clock-change[Defines a trigger based on system clock jumps]' \
39 '--on-startup=[Run SEC seconds after systemd was first started]:SEC' \
40 '--on-timezone-change[Defines a trigger based on system timezone changes]' \
41 '--on-unit-active=[Run SEC seconds after the last activation]:SEC' \
42 '--on-unit-inactive=[Run SEC seconds after the last deactivation]:SEC' \
[all …]
|
| /systemd-251/src/systemctl/ |
| D | systemctl-list-jobs.c | 61 const char *on, *off; in output_jobs_list() local
68 on = ansi_highlight_green(); in output_jobs_list()
71 printf("%sNo jobs %s.%s\n", on, skipped ? "listed" : "running", off); in output_jobs_list()
90 on = ansi_highlight(); in output_jobs_list()
92 on = ""; in output_jobs_list()
97 TABLE_SET_COLOR, on, in output_jobs_list()
100 TABLE_SET_COLOR, on); in output_jobs_list()
115 on = ansi_highlight(); in output_jobs_list()
118 printf("\n%s%u jobs listed%s.\n", on, n, off); in output_jobs_list()
|
| D | systemctl-list-units.c | 180 const char *on, *off; in output_units_list() local
190 on = ansi_highlight(); in output_units_list()
193 on = ansi_highlight_red(); in output_units_list()
200 on, records, off); in output_units_list()
204 on, records, off); in output_units_list()
353 const char *on, *off; in output_sockets_list() local
407 on = ansi_highlight(); in output_sockets_list()
410 on = ansi_highlight_red(); in output_sockets_list()
419 printf("\n%s%u sockets listed.%s\n", on, cs, off); in output_sockets_list()
602 const char *on, *off; in output_timers_list() local
[all …]
|
| D | systemctl-list-dependencies.c | 97 const char *on; in list_dependencies_one() local
105 on = ansi_highlight_green(); in list_dependencies_one()
110 on = ansi_normal(); in list_dependencies_one()
114 on = ansi_highlight_red(); in list_dependencies_one()
118 … printf("%s%s%s ", on, special_glyph(unit_active_state_to_glyph(active_state)), ansi_normal()); in list_dependencies_one()
|
| /systemd-251/src/shared/ |
| D | id128-print.c | 15 const char *on, *off; in id128_pretty_print_sample() local
18 on = ansi_highlight(); in id128_pretty_print_sample()
33 on, SD_ID128_FORMAT_VAL(id), off, in id128_pretty_print_sample()
34 on, SD_ID128_FORMAT_VAL(id), off, in id128_pretty_print_sample()
36 on, name); in id128_pretty_print_sample()
45 on, name, SD_ID128_FORMAT_VAL(id), off); in id128_pretty_print_sample()
|
| /systemd-251/docs/ |
| D | CGROUP_DELEGATION.md | 10 *Intended audience: hackers working on userspace subsystems that require direct
25 Before you read on, please make sure you read the low-level kernel
37 with cgroups and systemd, in particular as they shine more light on the various
43 Much of the philosophy behind these concepts is based on a couple of basic
61 software don't step on each other's toes constantly.
71 though it's a good thing to follow it then too. Rule #2 is not enforced on
83 cgroup trees to less privileged processes and so on, which all are not
84 available on cgroup v1.
111 software today and don't focus on the unified mode, then you are writing
125 `/sys/fs/cgroup/memory/foo/bar/`, `/sys/fs/cgroup/pids/foo/bar/`, and so on.
[all …]
|
| D | PREDICTABLE_INTERFACE_NAMES.md | 14 …eth0`, `eth1` and so on is generally not fixed anymore and it might very well happen that `eth0` o…
16 …on their MAC addresses. This turned out to have a multitude of problems, among them: this required…
18 …assign fixed names to interfaces which incorporate their physical location on the mainboard. In a …
22 …eralize the scheme pioneered by `biosdevname`. Assigning fixed names based on firmware/topology/lo…
29 1. Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: `eno1`)
54 * The same on all distributions that adopted systemd/udev
57 …eck first what the local interface name is before they can invoke commands on it, where previously…
66 1. You pass the `net.ifnames=0` on the kernel command line
|
| D | BLOCK_DEVICE_LOCKING.md | 11 [(`flock(2)`)](http://man7.org/linux/man-pages/man2/flock.2.html) on block
22 from processing rules on it — and thus bar it from probing the device — by
23 taking a BSD file lock on the block device node. Specifically, whenever
25 lock using [`flock(2)`](http://man7.org/linux/man-pages/man2/flock.2.html) on
26 the main block device (i.e. never on any partition block device, but on the
37 device while operating: before starting work on the block device, they should
38 take an `LOCK_EX` lock on it. This has two effects: first of all, in case
45 it implicitly releases the lock, so that `systemd-udevd` can process events on
51 locks being released. Such monitoring is not supported on Linux however, which
87 during normal operation, i.e. while file systems on it are mounted for
|
| D | TEMPORARY_DIRECTORIES.md | 11 provide for temporary files. The former is typically on `tmpfs` and thus
12 backed by RAM/swap, and flushed out on each reboot. The latter is typically a
61 turned on for a service (�� which is highly recommended), `/tmp/` and
68 recommended to turn this option on, it's highly recommended for applications
69 not to rely on this solely to avoid DoS vulnerabilities, because this option is
72 of defense, but should not be used as an excuse to rely on guessable names in
77 `/var/tmp/` for sharing files and directories. If this option is turned on this
95 temporary files it operates on to be suddenly removed. There are a couple of
99 operate on open, and only access the files through them. This way it doesn't
103 files right after creating them to ensure that on unexpected program
[all …]
|
| D | USER_NAMES.md | 10 The precise set of allowed user and group names on Linux systems is weakly
11 defined. Depending on the distribution a different set of requirements and
12 restrictions on the syntax of user/group names are enforced — on some
61 focus on Linux systems only however, hence those are out of scope. That said,
62 software like Samba is frequently deployed on Linux for providing compatibility
63 with Windows systems; on such systems it might be wise to stick to user/group
68 Distilled from the above, below are the rules systemd enforces on user/group
88 (typically 256 on Linux; rationale: this is how POSIX suggests to detect the
89 limit), `UT_NAMESIZE-1` (typically 31 on Linux; rationale: names longer than
91 accounting) and `NAME_MAX` (255 on Linux; rationale: user names typically
[all …]
|
| D | CODING_STYLE.md | 73 - `else` blocks should generally start on the same line as the closing `}`:
149 - Do not write functions that clobber call-by-reference variables on
151 variables only on success. The rule is: never clobber return parameters on
152 failure, always initialize return parameters on success.
174 much. systemd-internal headers must not rely on an include order, so it is
200 - Our focus is on the GNU libc (glibc), not any other libcs. If other libcs are
201 incompatible with glibc it's on them. However, if there are equivalent POSIX
261 - Instead of using `memzero()`/`memset()` to initialize structs allocated on
334 some exceptions: for constructors, it is OK to return `NULL` on OOM. For
341 - libc system calls typically return -1 on error (with the error code in
[all …]
|
| D | BUILDING_IMAGES.md | 17 maintained by the systemd project. If you are using or working on another image
24 instance should automatically acquire its own identifying credentials on first
31 will be auto-generated on first boot and thus be truly unique. If this file
39 which is used to seed the kernel's random pool on boot. If this file is
73 in order to allow multiple installations of the same OS on the same system
75 generated automatically on first boot: if the ID is not known before the first
79 Thus, for images that shall acquire their identity on first boot only, it is
100 on first boot as needed.
120 will component automatically populate `/etc/passwd` and `/etc/group` on
139 and robustly populated on first boot, so that the OS can safely boot up. Note
[all …]
|
| D | HOME_DIRECTORY.md | 26 user cannot make modifications to the file on their own (at least not without
35 `systemd-homed` is used (i.e. `--storage=directory` or `--storage=subvolume` on
54 `--storage=fscrypt` on the `homectl` command line.) Key management is
55 implemented via extended attributes on the directory itself: for each password
70 service at login, configured inside the user record. (Use `--storage=cifs` on
83 Linux file system inside a LUKS2 volume inside a loopback file (or on removable
84 media). (Use `--storage=luks` on the `homectl` command line.) Specifically:
99 same volume key, but based on its own IV.
109 The image file should reside in a directory `/home/` on the system,
114 When the image is stored on removable media (such as a USB stick), the image
[all …]
|
| D | CONTAINER_INTERFACE.md | 14 when systemd is used inside of an OS container. If you work on a container
26 read-only (the latter via e.g. a read-only bind mount on itself) in order
35 so on. If you do that, make sure to mark `/sys/` read-only, as that
46 or `/dev/stdout`, as systemd will do that on its own. Make sure to set up a
47 `BPF_PROG_TYPE_CGROUP_DEVICE` BPF program — on cgroupv2 — or the `devices`
48 cgroup controller — on cgroupv1 — so that no other devices but these may be
62 5. If systemd detects it is run in a container it will spawn a single shell on
63 `/dev/console`, and not care about VTs or multiple gettys on VTs. (But see
77 cgroup sub-tree of the container itself (on cgroupv2 in the unified
78 hierarchy, and on cgroupv1 in the `name=systemd` hierarchy) may be writable
[all …]
|
| D | GVARIANT-SERIALIZATION.md | 52 packet on dbus2 hence qualifies as a fully compliant GVariant
55 For details on gvariant, see:
69 on dbus2! In fact, the message size must be known in advance, from the
83 on the serialization size, as due to alignment for each 8bit
87 consider that on dbus1 the beginning of the fields array contains the
88 32bit array size (since that is how arrays are encoded on dbus1),
90 array, the size of the header on dbus1 and dbus2 stays identical, at
|
| D | ROOT_STORAGE_DAEMONS.md | 14 A number of complex storage technologies on Linux (e.g. RAID, volume
17 root file system of the Linux operating system is stored on such storage
25 this needs to be set up by the initial RAM file system (initrd), i.e. on Fedora
37 backing usually tried to maintain the root storage with program code stored on
39 detaching such a root file system becomes messy, since the program code on the
49 stored on the root file system itself.
110 for a daemon is to check for `/etc/initrd-release` (which exists on all modern
166 user commands or udev rules. Whenever a process is forked off on Unix it
185 to listen on on behalf of your daemon and minimally modify the daemon to
187 creating it on its own. Such modifications can be minimal, and are easily
[all …]
|
| D | PASSWORD_AGENTS.md | 10 …now this is used exclusively for encrypted hard-disk passphrases but later on this is likely to be…
21 * Create an inotify watch on /run/systemd/ask-password, watch for `IN_CLOSE_WRITE|IN_MOVED_TO`
22 * Ignore all events on files in that directory that do not start with "`ask.`"
24 …o ignore unknown `.ini` file keys in those files, so that we can easily extend the format later on.
32 …. In fact, the GNOME agent we ship does that, and you may simply piggyback on that, by executing "…
33 … of the password string either prefixed with "`+`" or with "`-`" depending on whether the password…
37 …on your environment you may either choose to show all outstanding passwords at the same time or in…
39 You may test this all with manually invoking the "`systemd-ask-password`" tool on the command line.…
|
| /systemd-251/test/units/ |
| D | testsuite-11.sh | 6 systemctl --no-block start fail-on-restart.service
7 active_state=$(systemctl show --value --property ActiveState fail-on-restart.service)
10 active_state=$(systemctl show --value --property ActiveState fail-on-restart.service)
12 systemctl is-failed fail-on-restart.service || exit 1
|
| D | testsuite-59.sh | 45 Description=TEST-59-RELOADING-RESTART Restart=on-failure
50 Restart=on-failure
57 Description=TEST-59-RELOADING-RESTART Restart=on-abort
62 Restart=on-abort
|
| /systemd-251/ |
| D | TODO | 23 * fedora: suggest auto-restart on failure, but not on success and not on coredump. also, ask people…
56 - instantiated apache, dovecot and so on
103 kernel PCR state, without breaking things on every kernel update. As long as
107 on the measured kernel/initrd of course, thus we cannot put the signature
153 on subsequent boots. Then provide a tool to sign code with the key in the
175 * add a clear concept how the initrd can make up credentials on their own to
181 depending on whether a specific system credential is set. Usecase: a service
191 for it, or when read() returns EAGAIN or on IN_Q_OVERFLOW. Then, whenever we
198 creds, sysexts and so on. similar to existing variable of sd-boot
210 on verification if in secureboot mode
[all …]
|
| D | LICENSE.GPL2 | 45 software. If the software is modified by someone else and passed on, we
47 that any problems introduced by others will not reflect on the original
65 refers to any such program or work, and a "work based on the Program"
75 is covered only if its contents constitute a work based on the
77 Whether that is true depends on what the Program does.
81 conspicuously and appropriately publish on each copy an appropriate
91 of it, thus forming a work based on the Program, and copy and
111 does not normally print such an announcement, your work based on
120 on the Program, the distribution of the whole must be on the terms of
127 collective works based on the Program.
[all …]
|
| D | README | 14 #systemd on irc.libera.chat
78 Some udev rules and virtualization detection relies on it:
167 If systemd is compiled with libseccomp support on architectures which do
171 with audit being enabled. This works correctly only on kernels 3.14 and
249 nss-systemd must be enabled on systemd systems, as that's required for
255 systemd relies on — such as D-Bus — really should use the same prefix,
256 otherwise you are on your own.) -Dsplit-usr=false (which is the default
273 expected to compile on current versions of popular distributions (at
278 Features which would break compilation on slightly-older distributions
285 tested on popular architectures (currently amd64, i386, arm64, ppc64el,
[all …]
|
| D | LICENSE.LGPL2.1 | 25 strategy to use in any particular case, based on the explanations below.
54 modified by someone else and passed on, the recipients should know
89 For example, on rare occasions, there may be a special need to
111 "work based on the library" and a "work that uses the library". The
129 which has been distributed under these terms. A "work based on the
146 on the Library (independent of the use of the Library in a tool for
147 writing it). Whether that is true depends on what the Library does
152 you conspicuously and appropriately publish on each copy an
163 of it, thus forming a work based on the Library, and copy and
196 on the Library, the distribution of the whole must be on the terms of
[all …]
|
| /systemd-251/rules.d/ |
| D | 60-autosuspend.rules | 1 # do not edit this file, it will be overwritten on update
7 ATTR{power/control}="on", GOTO="autosuspend_end"
9 # Enable autosuspend if hwdb says so. Here we are relying on
10 # the hwdb import done earlier based on MODALIAS.
|