latter it takes precedence over the former, similar to how most of
systemd's own configuration is handled. Given that PAM stack
definitions are primarily put together by OS vendors/distributions
- (though possibly overriden by users), this systemd release moves its
+ (though possibly overridden by users), this systemd release moves its
own PAM stack configuration for the "systemd-user" PAM service (i.e.
for the PAM session invoked by the per-user user@.service instance)
from /etc/pam.d/ to /usr/lib/pam.d/. We recommend moving all
/etc/pam.d/ to /usr/lib/pam.d/, but if such OS-wide migration is not
desired the location to which systemd installs its PAM stack
configuration file may be changed via the "pamconfdir" meson variable
- at build time, optionally undoing ths change of default paths
+ at build time, optionally undoing this change of default paths
introduced with systemd 247.
CHANGES WITH 246:
generation for collection with systemd-pstore.
* We provide a set of udev rules to enable auto-suspend on PCI and USB
- devices that were tested to currectly support it. Previously, this
+ devices that were tested to correctly support it. Previously, this
was distributed as a set of udev rules, but has now been replaced by
by a set of hwdb entries (and a much shorter udev rule to take action
if the device modalias matches one of the new hwdb entries).
</term>
<listitem><para>Reconfigure network interfaces. Takes interface name or index number. Note that
this does not reload <filename>.netdev</filename> or <filename>.network</filename>
- corresponding to the the specifed interface. So, if you edit config files, it is necessary to
+ corresponding to the the specified interface. So, if you edit config files, it is necessary to
call <command>networkctl reload</command> first to apply new settings.</para></listitem>
</varlistentry>
specifies the initial size of the loopback file to create.</para>
<para>The <option>--size=auto</option> option takes the sizes of pre-existing partitions into
- account. However, it does not accomodate for partition tables that are not tightly packed: the
+ account. However, it does not accommodate for partition tables that are not tightly packed: the
configured partitions might still not fit into the backing device if empty space exists between
pre-existing partitions (or before the first partition) that cannot be fully filled by partitions to
grow or create.</para>
</para>
<para>If the address string is a string in the format
- <literal><replaceable>v.w.x.y</replaceable>:<replaceable>z</replaceable></literal>, it is interpeted
+ <literal><replaceable>v.w.x.y</replaceable>:<replaceable>z</replaceable></literal>, it is interpreted
as IPv4 address <replaceable>v.w.x.y</replaceable> and port <replaceable>z</replaceable>.</para>
<para>If the address string is a string in the format
<literal>[<replaceable>x</replaceable>]:<replaceable>y</replaceable></literal>, it is interpreted as
IPv6 address <replaceable>x</replaceable> and port <replaceable>y</replaceable>. An optional
- interface scope (interface name or number) may be specifed after a <literal>%</literal> symbol:
+ interface scope (interface name or number) may be specified after a <literal>%</literal> symbol:
<literal>[<replaceable>x</replaceable>]:<replaceable>y</replaceable>%<replaceable>dev</replaceable></literal>.
Interface scopes are only useful with link-local addresses, because the kernel ignores them in other
cases. Note that if an address is specified as IPv6, it might still make the service available via
<varlistentry id='tclass-classid'>
<term><varname>ClassId=</varname></term>
<listitem>
- <para>Configues the unique identifier of the class. It is specified as the major and minor numbers in
+ <para>Configures the unique identifier of the class. It is specified as the major and minor numbers in
hexadecimal in the range 0x1–Oxffff separated with a colon (<literal>major:minor</literal>).
Defaults to unset.</para>
</listitem>
* bottleneck we can certainly place an in-memory hash table in front of this, but for the beginning,
* let's keep things simple, and just use the disk as lookup table for inodes.
*
- * Note that this should have zero performace impact as long as .n_link of all files copied remains
+ * Note that this should have zero performance impact as long as .n_link of all files copied remains
* <= 0, because in that case we will not actually allocate the hardlink inode lookup table directory
* on disk (we do so lazily, when the first candidate with .n_link > 1 is seen). This means, in the
* common case where hardlinks are not used at all or only for few files the fact that we store the
if (dfd < 0)
return -errno;
- /* First we use the literally specified credentials. Note that they might be overriden again below,
+ /* First we use the literally specified credentials. Note that they might be overridden again below,
* and thus act as a "default" if the same credential is specified multiple times */
HASHMAP_FOREACH(sc, context->set_credentials) {
size_t add;
* Yes it's nasty playing games with /dev/ and /dev/shm/ like this, since it does not exist
* for this purpose, but there are few other candidates that work equally well for us, and
* given that the we do this in a privately namespaced short-lived single-threaded process
- * that noone else sees this should be OK to do.*/
+ * that no one else sees this should be OK to do.*/
if (mount(NULL, "/dev", NULL, MS_SLAVE|MS_REC, NULL) < 0) /* Turn off propagation from our namespace to host */
goto child_fail;
* we'll try not to call PR_SET_SECUREBITS unless necessary. Setting securebits requires
* CAP_SETPCAP. */
if (prctl(PR_GET_SECUREBITS) != secure_bits) {
- /* CAP_SETPCAP is required to set securebits. This capabilitiy is raised into the
+ /* CAP_SETPCAP is required to set securebits. This capability is raised into the
* effective set here.
* The effective set is overwritten during execve with the following values:
* - ambient set (for non-root processes)
/* Also create /run/systemd/inaccessible nodes, so that we always have something to mount
* inaccessible nodes from. If we run in a container the host might have created these for us already
- * in /run/host/inaccessible/. Use those if we can, since tht way we likely get access to block/char
+ * in /run/host/inaccessible/. Use those if we can, since that way we likely get access to block/char
* device nodes that are inaccessible, and if userns is used to nodes that are on mounts owned by a
* userns outside the container and thus nicely read-only and not remountable. */
if (access("/run/host/inaccessible/", F_OK) < 0) {
if (disk_uuid_path)
(void) ioctl(image_fd, BLKRRPART, 0);
else {
- /* If we operate on a file, sync the contaning directory too. */
+ /* If we operate on a file, sync the containing directory too. */
r = fsync_directory_of_file(image_fd);
if (r < 0) {
log_error_errno(r, "Failed to synchronize directory of image file to disk: %m");
r = dhcp4_start_acd(link);
if (r < 0)
- return log_link_error_errno(link, r, "Failed to start IPv4ACD for DHCP4 adddress: %m");
+ return log_link_error_errno(link, r, "Failed to start IPv4ACD for DHCP4 address: %m");
dhcp4_check_ready(link);
return 0;
/* Hard lower limit for new partition sizes */
#define HARD_MIN_SIZE 4096
-/* libfdisk takes off sightly more than 1M of the disk size when creating a GPT disk label */
+/* libfdisk takes off slightly more than 1M of the disk size when creating a GPT disk label */
#define GPT_METADATA_SIZE (1044*1024)
/* LUKS2 takes off 16M of the partition size with its metadata by default */
if (r < 0)
goto fail;
- /* Do not set IP_TTL for extra DNS stub listners, as the address may not be local and in that case
+ /* Do not set IP_TTL for extra DNS stub listeners, as the address may not be local and in that case
* people may want ttl > 1. */
r = socket_set_freebind(fd, l->family, true);
if (!cache)
return -ENOMEM;
- /* The directory list is harcoded here: /etc is the standard, and rpm-ostree uses /usr/lib. This
+ /* The directory list is hardcoded here: /etc is the standard, and rpm-ostree uses /usr/lib. This
* could be made configurable, but I don't see the point right now. */
const char *fname;
/* The type of recovery key, must be "modhex64" right now */
char *type;
- /* A UNIX pasword hash of the normalized form of modhex64 */
+ /* A UNIX password hash of the normalized form of modhex64 */
char *hashed_password;
} RecoveryKey;
continue;
/* If statx() is supported, use it. It's preferable over fstatat() since it tells us
- * explicitly where we are looking at a mount point, for free as side information. Determing
+ * explicitly where we are looking at a mount point, for free as side information. Determining
* the same information without statx() is hard, see the complexity of path_is_mount_point(),
* and also much slower as it requires a number of syscalls instead of just one. Hence, when
* we have modern statx() we use it instead of fstat() and do proper mount point checks,
projects / thirdparty / systemd.git / commitdiff
