Home
last modified time | relevance | path

Searched refs:it (Results 1 – 25 of 485) sorted by relevance

12345678910>>...20

/systemd-251/docs/
DBLOCK_DEVICE_LOCKING.md22 from processing rules on it — and thus bar it from probing the device — by
24 `systemd-udevd` starts processing a block device it takes a `LOCK_SH|LOCK_NB`
28 returns `EAGAIN`), it refrains from processing the device. If it manages to take
29 the lock it is kept for the entire time the device is processed.
31 Note that `systemd-udevd` also watches all block device nodes it manages for
38 take an `LOCK_EX` lock on it. This has two effects: first of all, in case
39 `systemd-udevd` is still processing the device the tool will wait for it to
40 finish. Second, after the lock is taken, it can be sure that `systemd-udevd`
42 applications subscribed to it won't get device notifications from potentially
45 it implicitly releases the lock, so that `systemd-udevd` can process events on
[all …]
DCGROUP_DELEGATION.md19 times. However, it has been updated and improved substantially, even
47 1. The **no-processes-in-inner-nodes** rule: this means that it's not permitted
50 it's an inner node it may not contain processes directly, and if it's a leaf
51 node then it may not have child cgroups. (Note that there are some minor
57 writer, i.e. a single process managing it. It's OK if different cgroups have
59 specific cgroup, and when it does that ownership is exclusive, and nothing else
60 should manipulate it at the same time. This rule ensures that various pieces of
69 soon as you add a process to a cgroup it is ensured the rule is not
71 though it's a good thing to follow it then too. Rule #2 is not enforced on
73 root can do anything, modulo SELinux and friends), but if you ignore it you'll
[all …]
DCODING_STYLE.md23 overdo it, ~109ch should be enough really. The `.editorconfig`, `.vimrc` and
29 - If you break a function declaration over multiple lines, do it like this:
93 i.e. use an enum for it, if possible. Indicate bit values via `1 <<`
95 it.
111 this is not a regular enum value, prefix it with `_`. Also, define a special
112 "invalid" enum value, and set it to `-EINVAL`. That way the enum type can
132 below.) Both for internal and external code it's OK to use even newer
142 environments, at least the library code should make sure it works correctly
174 much. systemd-internal headers must not rely on an include order, so it is
185 library-like code it is important to avoid global variables. Why are global
[all …]
DNETWORK_ONLINE.md18 `network-pre.target` is a passive unit: it cannot be started directly and it is
20 wants to run before it must pull it in. Network management services hence
31 Ordering after it it has little meaning during start-up: whether any network
32 interfaces are already configured when it is reached is not defined.
36 any unit that has `After=network.target` can be sure that it is *stopped*
41 Note that `network.target` is a passive unit: you cannot start it directly and
42 it is not pulled in by any services that want to make use of the network.
43 Instead, it is pulled in by the network management services
52 software. Usually it indicates a configured, routable IP address of some
56 It is an active target, meaning that it may be pulled in by the services
[all …]
DRANDOM_SEEDS.md20 it. This entropy pool needs to be initialized with a minimal level of entropy
21 before it can provide high quality, cryptographic random numbers to
48 Note that the time it takes to initialize the random pool may differ between
61 to credit entropy for it (i.e. data from this source wasn't considered good
62 enough to consider the entropy pool properly filled even though it was
86 to kernel mode Linux will query some random data through it, and feed it into
87 the pool, but not credit entropy to it. What kind of random source is behind
88 the EFI RNG API is often not entirely clear, but it hopefully is some kind of
99 userspace process the kernel invokes. Because of that it runs at a time where
109 * systemd assigns 'invocation' UUIDs to all services it invokes that uniquely
[all …]
DUIDS-GIDS.md14 aren't IRL. With that in mind, when we discuss UIDs below it should be assumed
30 `systemd`. If you do change it you void your warranty.) Because Fedora is a
69 available regular user range only, usually 1000..60000. And it's also usually
81 above). However, it does define some special group/GID assignments, which are
91 group must have the GID 5. That's because it must be encoded in the `devpts`
104 might get different UIDs assigned in case of conflict, though it is
111 range has been chosen so that it is below the 16bit boundary (i.e. below
125 `-U`) then it will automatically find a so far unused 16bit subrange of this
126 range and assign it to the container. The range is picked so that the upper
133 range is above the 16bit boundary. Moreover it's below the 31bit boundary,
[all …]
DAUTOMATIC_BOOT_ASSESSMENT.md31 successful, thus turning off boot counting for it.
41 completed successfully. When enabled it becomes an indirect dependency of
64 counting is enabled for it. The first number is the "tries left" counter
67 it have already been made. Each time a boot loader entry marked this way is
69 one. (If the second counter is missing, then it is assumed to be equivalent to
72 it reached zero the entry is not tried anymore (entry state "bad"). If the boot
83 loader entry file for it. Let's say the version string for the new kernel is
95 `4.14.11-300.fc27.x86_64+1-2.conf`, and boot it.
99 `4.14.11-300.fc27.x86_64+0-3.conf` and boot it.
143 renames it dropping the counter tag. Thus
[all …]
DCONTAINER_INTERFACE.md20 running systemd it may just set it before invoking systemd, and systemd will
21 leave it unmodified when there is no hostname configured in `/etc/hostname`
29 enabled, feel free to make `/proc/sys/net/` writable. If it also has user, ipc,
42 ttys, to avoid being killed by SAK. It only opens ttys for the time it
51 for them for which it needs to be able to create these device nodes.
62 5. If systemd detects it is run in a container it will spawn a single shell on
67 that to systemd which will do so if they are missing. Note that it is
86 it. This ensures that the unit you created will be part of all cgroup
96 1. To allow systemd (and other programs) to identify that it is executed within
118 container's PID 1 to tell it on which ptys to spawn gettys. The variable
[all …]
DBUILDING_IMAGES.md12 disk and booting it up. When building such "golden" OS images for
18 builder it's recommended to keep the following concepts and recommendations in
25 boot. For that it's essential to:
29 file or write the string `uninitialized\n` into it. This file is supposed to
30 carry a 128bit identifier unique to the system. Only when it is reset it
76 boot it cannot be used to name the most basic resources required for the boot
79 Thus, for images that shall acquire their identity on first boot only, it is
83 resources of the OS. If not configured explicitly it defaults to the machine
98 it's relatively easy to build images that only ship a `/usr/` tree, and
157 Typically, if an image is `dd`-ed onto a target disk it will be minimal:
[all …]
DRESOLVED-VPNS.md45 configured on it, then any lookups for names ending in `.foo.com` (or for
51 single-label domain names. When it comes to routing assigning a routing
53 it.
73 instead of `~.` — would have the same effect, but given that it's mostly
74 pointless to suffix an unqualified domain with `.`, we generally declare it
77 Routing domains also have particular relevance when it comes to the reverse
82 domain names for IPv4 addresses 192.168.x.y are preferable routed to it.
108 server, since it matches by three suffix labels instead of just two. The fact
115 ## Putting it Together
123 2. One VPN interface of the *privacy* kind, maybe called `privacy0`. When it is
[all …]
DBOOT_LOADER_SPECIFICATION.md47 configuration of it freely. Other Linux installs have to be manually
75 system, it provides a boot options logic that can offer similar
76 functionality. Here's why we think that it is not enough for our uses:
85 menu item information on disk, it is always available, regardless if the BIOS
104 partition with the type id of 0xEA already exists it should be used as
108 (let's say 500MB), and it should be used as `$BOOT`.
112 GUID of `bc13c2ff-59e6-4262-a352-b275fd6f7172`, already exists, it should
117 (let's say 250MB) and otherwise qualifies, it should be used as `$BOOT`.
162 directory inside the file system (see below), but it doesn't intend to define
194 installations. More specifically it is suggested to include the machine ID
[all …]
DTEMPORARY_DIRECTORIES.md40 drop-ins. However this is not recommended, as it is fully safe only if these
67 ones. This reduces the surface for local DoS attacks substantially. While it is
68 recommended to turn this option on, it's highly recommended for applications
75 temporary files stored in it is substantially different from the case where
87 `systemd-tmpfiles` btw, it's inherited from previous subsystems such as
94 other hand it creates problems for long-running software that does not expect
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
102 reading and writing. When operating this way it is recommended to delete the
123 descriptors opened by a process are implicitly closed when it exits, this is
[all …]
DCONVERTING_TO_HOMED.md14 it might be desirable to convert an existing, traditional user account to a
49 related files. We want to use the same data for the new record, hence it's good
63 your user's main group. Depending on your distribution it's a group private
73 your user. If it doesn't match (and is something like `users`) it apparently
103 group as new primary group, but will have it as auxiliary group.
112 5. Your new user account exists now, but it has an empty home directory. Let's
113 now migrate your old home directory into it. For that let's mount the new
128 it hence:
134 And that's it, we are done already. You can log out now and should be able to
DROOT_STORAGE_DAEMONS.md28 and unmounting all file systems it can (which means excluding the root fs)
29 systemd will jump back into the initrd code allowing it to unmount the final
32 detach/unmount the root fs, i.e. inverting the exact commands it used to set
47 where the storage daemons are being run from the storage it maintains
67 it entirely replaces the systemd init process) then iterates through the
99 And that's already it. Note that this functionality is only to be used by
154 If your daemon implements the logic pointed out above it should work nicely
155 from initrd environments. In many cases it might be necessary to additionally
161 * If your storage daemon is run from the main OS (i.e. not the initrd) it will
166 user commands or udev rules. Whenever a process is forked off on Unix it
[all …]
DJOURNAL_FILE_FORMAT.md43 stream-based nature it is not indexed.
76 …ed, more specifically `jenkins_hashlittle2()` with the first 32bit integer it returns as higher 32…
86 If any kind of corruption is noticed by a writer it should immediately rotate
88 original file, but it should be left around so that as little data as possible
91 If any kind of corruption is noticed by a reader it should try hard to handle
93 to as much data around it as possible.
95 A reader should verify all offsets and other data as it reads it. This includes
97 trying to read it via a memory map.
143 The Header struct defines, well, you guessed it, the file header:
186 the machine it is running on it should immediately rotate the file and start a
[all …]
/systemd-251/
DLICENSE.GPL27 of this license document, but changing it is not allowed.
12 freedom to share and change it. By contrast, the GNU General Public
17 using it. (Some other Free Software Foundation software is covered by
18 the GNU Lesser General Public License instead.) You can apply it to
24 this service if you wish), that you receive source code or can get it
25 if you want it, that you can change the software or use pieces of it
31 distribute copies of the software, or if you modify it.
53 program proprietary. To prevent this, we have made it clear that any
63 a notice placed by the copyright holder saying it may be distributed
67 that is to say, a work containing the Program or a portion of it,
[all …]
DLICENSE.LGPL2.17 of this license document, but changing it is not allowed.
16 freedom to share and change it. By contrast, the GNU General Public
22 Free Software Foundation and other authors who decide to use it. You
23 can use it too, but we suggest you first think carefully about whether
31 it if you want it; that you can change the software and use pieces of
32 it in new free programs; and that you are informed that you can do
38 you if you distribute copies of the library or if you modify it.
46 it. And you must show them these terms so they know their rights.
52 To protect each distributor, we want to make it very clear that
81 We call this license the "Lesser" General Public License because it
[all …]
DTODO17 - teach dbus to activate all services it finds in /etc/systemd/services/org-*.service
27 … declare access mode and ownership of unit files to root:root 0644, and add an rpmlint check for it
37 * If timer has just OnInactiveSec=..., it should fire after a specified time
41 - hwdb: what belongs into it, lsusb
92 container managers find it. the ~/.identity file is also a candidate for a
93 file to move there, since it is managed by privileged code (i.e. homed) and
110 of its own, because then it is next to the kernel and initrd which after all
119 policies (e.g. the string like "4+7+9") so that it can also include explicit
130 to target dir in /tmp, and bind through it.
151 it. when developer mode is entered generate a key pair in the TPM2, and add
[all …]
/systemd-251/LICENSES/
DLGPL-2.0-or-later.txt8 …ed to copy and distribute verbatim copies of this license document, but changing it is not allowed.
10 [This is the first released version of the library GPL. It is numbered 2 because it goes with vers…
14 The licenses for most software are designed to take away your freedom to share and change it. By co…
16 …n software, and to any other libraries whose authors decide to use it. You can use it for your lib…
18 … that you receive source code or can get it if you want it, that you can change the software or us…
20 …e to certain responsibilities for you if you distribute copies of the library, or if you modify it.
22 …them with the library, after making changes to the library and recompiling it. And you must show t…
28 …rming the program into proprietary software. To prevent this, we have made it clear that any paten…
30 …te different from the ordinary one; be sure to read it in full, and don't assume that anything in
32it. Linking a program with a library, without changing the library, is in some sense simply using …
[all …]
/systemd-251/units/
Dsystemd-time-wait-sync.service.in5 # systemd is free software; you can redistribute it and/or modify it
14 # Note that this tool doesn't need CAP_SYS_TIME itself, but it's primary
18 # make this all "just work" for the general case, and leave it to local
19 # modifications to make it work in the remaining cases.
Dsys-fs-fuse-connections.mount5 # systemd is free software; you can redistribute it and/or modify it
21 # loaded. Indeed udev starts this unit when it receives an uevent for the
22 # module but the kernel sends it too early, ie before the init() of the module
Dsys-kernel-config.mount5 # systemd is free software; you can redistribute it and/or modify it
20 # loaded. Indeed udev starts this unit when it receives an uevent for the
21 # module but the kernel sends it too early, ie before the init() of the module
/systemd-251/src/test/
Dtest-nss-hosts.c48 for (const struct gaih_addrtuple *it = tuples; it; it = it->next) { in print_gaih_addrtuples() local
53 memcpy(&u, it->addr, 16); in print_gaih_addrtuples()
54 r = in_addr_to_string(it->family, &u, &a); in print_gaih_addrtuples()
57 assert_se(a = hexmem(it->addr, 16)); in print_gaih_addrtuples()
60 it->name, in print_gaih_addrtuples()
61 af_to_string(it->family, family_name, sizeof family_name), in print_gaih_addrtuples()
63 FORMAT_IFNAME_FULL(it->scopeid, FORMAT_IFNAME_IFINDEX_WITH_PERCENT)); in print_gaih_addrtuples()
/systemd-251/test/fuzz/fuzz-udev-rules/
D78-sound-card.rules1 # do not edit this file, it will be overwritten on update
11 # The story goes like this: when ALSA registers a new sound card it emits a
13 # child device nodes that belong to it. udev relays those to applications,
17 # before it. However unfortunately due to the fact that siblings are forwarded
20 # OTOH before an application can open a device it needs to make sure that all
27 # When an application needs to listen for appearing devices it can hence look
31 # in it may need to figure out if the 'change' event has already been triggered
/systemd-251/rules.d/
D78-sound-card.rules1 # do not edit this file, it will be overwritten on update
11 # The story goes like this: when ALSA registers a new sound card it emits a
13 # child device nodes that belong to it. udev relays those to applications,
17 # before it. However unfortunately due to the fact that siblings are forwarded
20 # OTOH before an application can open a device it needs to make sure that all
27 # When an application needs to listen for appearing devices it can hence look
31 # in it may need to figure out if the 'change' event has already been triggered

12345678910>>...20