* `$SYSTEMD_HOME_DEBUG_SUFFIX` – takes a short string that is suffixed to
`systemd-homed`'s D-Bus and Varlink service names/sockets. This is also
- understood by `homectl`. This too is useful for running an additiona copy of
+ understood by `homectl`. This too is useful for running an additional copy of
`systemd-homed` that doesn't interfere with the host's main one.
* `$SYSTEMD_HOMEWORK_PATH` – configures the path to the `systemd-homework`
home directory remains in unclean state if the storage device is removed from
the system by the user).
-`accessMode` → The access mode currently in effect for the home directory iself.
+`accessMode` → The access mode currently in effect for the home directory
+itself.
`fileSystemType` → The file system type backing the home directory: a short
string, such as "btrfs", "ext4", "xfs".
<para><function>sd_event_source_set_ratelimit_expire_callback</function> may be used to set a callback
function that is invoked every time the event source leaves rate limited state. Note that function is
- called in the same event loop iteration in which state transition occured.</para>
+ called in the same event loop iteration in which state transition occurred.</para>
<para>Rate limiting is currently implemented for I/O, timer, signal, defer and inotify event
sources.</para>
to the processes themselves to close them after use or whether to leave them open until the process exits
(in which case the kernel closes them automatically). Note that the file descriptors received by daemons
are duplicates of the file descriptors the service manager originally allocated and bound and of which it
- continously keeps a copy (except if <varname>Accept=yes</varname> is used). This means any socket option
+ continuously keeps a copy (except if <varname>Accept=yes</varname> is used). This means any socket option
changes and other changes made to the sockets will visible to the service manager too. Most importanly
this means it's generally not a good idea to invoke <citerefentry
project='man-pages'><refentrytitle>shutdown</refentrytitle><manvolnum>2</manvolnum></citerefentry> on
The second parameter will be interpreted as a destination path that will be created as a symlink to the directory.
The symlinks will be created after any <varname>BindPaths=</varname> or <varname>TemporaryFileSystem=</varname>
options have been set up, to make ephemeral symlinking possible. The same source can have multiple symlinks, by
- using the same first parameter, but a diferent second parameter.</para></listitem>
+ using the same first parameter, but a different second parameter.</para></listitem>
<para>The directories defined by these options are always created under the standard paths used by systemd
(<filename>/var/</filename>, <filename>/run/</filename>, <filename>/etc/</filename>, …). If the service needs
mqueue, {MQUEUE_MAGIC}
# msdos is an older legacy version of vfat, shares the magic
msdos, {MSDOS_SUPER_MAGIC}
-# ncp/ncpfs have been removed from the kernel, but ncpfs was the offical name
+# ncp/ncpfs have been removed from the kernel, but ncpfs was the official name
ncp, {NCP_SUPER_MAGIC}
ncpfs, {NCP_SUPER_MAGIC}
# nfs is the old version of nfs4, and they share the same magic
if efi_arch.length() == 0
if get_option('gnu-efi') == 'true'
- error('gnu-efi support requested, but headers not found or efi arch is unkown')
+ error('gnu-efi support requested, but headers not found or efi arch is unknown')
endif
warning('gnu-efi headers not found or efi arch is unkown, disabling gnu-efi support')
subdir_done()
assert(*b);
/* Order user records by their weight (and by their name, to make things stable). We put the records
- * with the heighest weight last, since we distribute space from the beginning and round down, hence
+ * with the highest weight last, since we distribute space from the beginning and round down, hence
* later entries tend to get slightly more than earlier entries. */
r = CMP(user_record_rebalance_weight((*a)->record), user_record_rebalance_weight((*b)->record));
log_debug("Rebalancing now...");
/* We maintain a simple state engine here to keep track of what we are doing. We'll first shrink all
- * homes that shall be shrinked and then grow all homes that shall be grown, so that they can take up
+ * homes that shall be shrunk and then grow all homes that shall be grown, so that they can take up
* the space now freed. */
for (;;) {
temporary = TAKE_PTR(d); /* Needs to be destroyed now */
/* Let's decouple namespaces now, so that we can possibly mount a UID map mount into
- * /run/systemd/user-home-mount/ that noone will see but us. */
+ * /run/systemd/user-home-mount/ that no one will see but us. */
r = home_unshare_and_mkdir();
if (r < 0)
return r;
if (fstatfs(fd, &sfs) < 0)
return log_error_errno(errno, "Failed to statfs() home file system: %m");
- /* Let's determine the minimal file syste size of the used fstype */
+ /* Let's determine the minimal file system size of the used fstype */
minsz = minimal_size_by_fs_magic(sfs.f_type);
if (minsz == UINT64_MAX)
return log_error_errno(SYNTHETIC_ERRNO(EOPNOTSUPP), "Don't know minimum file system size of file system type '%s' of home directory.", fs_type_to_string(sfs.f_type));
/* So here's the thing: we enable "deferred deactivation" on our dm-crypt volumes. This means they
* are automatically torn down once not used anymore (i.e. once unmounted). Which is great. It also
* means that when we deactivate a home directory and try to tear down the volume that backs it, it
- * possibly is aleady torn down or in the process of being torn down, since we race against the
+ * possibly is already torn down or in the process of being torn down, since we race against the
* automatic tearing down. Which is fine, we handle errors from that. However, we lose the ability to
* naturally wait for the tear down operation to complete: if we are not the ones who tear down the
* device we are also not the ones who naturally block on that operation. Hence let's add some code
* repeat that here */
return r;
- /* If a higher log level is requested, the generate a non-debug mesage here too. */
+ /* If a higher log level is requested, the generate a non-debug message here too. */
return log_full_errno(level, r, "Failed to unmount mount tree below %s: %m", HOME_RUNTIME_WORK_DIR);
}
assert(in6_addr_is_link_local(&link->ipv6ll_address));
if (link_get_dhcp6_client_start_mode(link) != DHCP6_CLIENT_START_MODE_NO)
- /* When WithoutRA= is specified, then the DHCPv6 client should be already runnging in
+ /* When WithoutRA= is specified, then the DHCPv6 client should be already running in
* the requested mode. Hence, ignore the requests by RA. */
return 0;
offset = round_up_size(offset, 4096);
next = round_down_size(next, 4096);
- *ret = LESS_BY(next, offset); /* Saturated substraction, rounding might have fucked things up */
+ *ret = LESS_BY(next, offset); /* Saturated subtraction, rounding might have fucked things up */
return 0;
}
const char *dir; /* directory or symlink to create */
mode_t mode;
const char *target; /* if non-NULL create as symlink to this target */
- const char *exists; /* conditionalize this entry on existance of this file */
+ const char *exists; /* conditionalize this entry on existence of this file */
bool ignore_failure;
} BaseFilesystem;
return 0;
#else
- return log_warning_errno(SYNTHETIC_ERRNO(EOPNOTSUPP), "Seccomp support or close_range() syscall definition not availeble.");
+ return log_warning_errno(SYNTHETIC_ERRNO(EOPNOTSUPP), "Seccomp support or close_range() syscall definition not available.");
#endif
}
# Cause the generator to re-run
systemctl daemon-reload || exit 1
- # Check for existance of unit files...
+ # Check for existence of unit files...
if [[ ! -e "/run/systemd/generator/systemd-integritysetup@${DM_NAME}.service" ]]; then
echo "Service file does not exist!"
exit 1
systemctl stop systemd-integritysetup@"${DM_NAME}".service || exit 1
if [ -e "${FULL_DM_DEV_NAME}" ]; then
- echo "Expecting ${FULL_DM_DEV_NAME} to not exist after stoping unit!"
+ echo "Expecting ${FULL_DM_DEV_NAME} to not exist after stopping unit!"
exit 1
fi
projects / thirdparty / systemd.git / commitdiff
