Lines Matching refs:of

12 This section will attempt to provide a high-level overview of the various
13 components of the systemd repository.
17 Directories in `src/` provide the implementation of all daemons, libraries and
24 You might wonder what kind of common code belongs in `src/shared/` and what
37 - may not use any code outside of `src/basic/`
41 - may not use any code outside of `src/basic/`, `src/libsystemd/`
47 - may not use any code outside of `src/basic/`, `src/libsystemd/`, `src/shared/`
51 Code located in `src/core/` implements the main logic of the systemd system (and user)
58 The system and session manager supports a large number of unit settings. These can generally
88 corresponding module. While most of the tests can be run by any user, some
90 (mostly in the form of effective capabilities). These tests are self-contained,
98 Fuzzers are a type of unit tests that execute code on an externally-supplied
100 `src/shared` live under `src/fuzz/`, and those for other parts of the codebase
104 each fuzzer. Some of the files are "seed corpora", i.e. files that contain
105 lists of settings and input values intended to generate initial coverage, and
109 short-but-meaningful names. Names of meson tests include the input file name
113 as a normal executable and executed for each of the input samples under
114 `test/fuzz/` as part of the test suite. Secondly, fuzzers may be instrumented
115 with sanitizers and invoked as part of the test suite (if `-Dfuzz-tests=true`
129 Most of those tests should be able to run via `systemd-nspawn`, which is
130 orders-of-magnitude faster than `qemu`, but some tests require privileged
139 under `hwdb.d/`. Some of these files are updated automatically, some are filled
149 `meson test -C build/ github-pages` run as part of the CI.