https://bugs.freedesktop.org/show_bug.cgi?id=54501
24 files changed:
target units are available, as listed on
<citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
target units are available, as listed on
<citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
- <para>The follow chart is a structural overview of
+ <para>The following chart is a structural overview of
these well-known units and their position in the
boot-up logic. The arrows describe which units are
pulled in and ordered before which other units. Units
these well-known units and their position in the
boot-up logic. The arrows describe which units are
pulled in and ordered before which other units. Units
<varlistentry>
<term><varname>verify</varname></term>
<varlistentry>
<term><varname>verify</varname></term>
- <listitem><para> If the the encryption
+ <listitem><para> If the encryption
password is read from console, it has
to be entered twice (to prevent
typos). </para></listitem>
password is read from console, it has
to be entered twice (to prevent
typos). </para></listitem>
<term><varname>timeout=</varname></term>
<listitem><para>Specify the timeout
<term><varname>timeout=</varname></term>
<listitem><para>Specify the timeout
- for querying for a password. If not
- unit is specified in
- seconds. Supported units are s, ms,
+ for querying for a password. If no
+ unit is specified seconds is used.
+ Supported units are s, ms,
us, min, h, d.</para></listitem>
</varlistentry>
us, min, h, d.</para></listitem>
</varlistentry>
<function>exit()</function> in the
original process. The process that
invoked the daemon must be able to
<function>exit()</function> in the
original process. The process that
invoked the daemon must be able to
<function>exit()</function> happens
after initialization is complete and
all external communication channels
<function>exit()</function> happens
after initialization is complete and
all external communication channels
accessible.</para></listitem>
</orderedlist>
accessible.</para></listitem>
</orderedlist>
compatibility with SysV systems should
implement the scheme pointed out
above. However, it is recommended to make this
compatibility with SysV systems should
implement the scheme pointed out
above. However, it is recommended to make this
- behaviour optional and configurable via a
+ behavior optional and configurable via a
command line argument, to ease debugging as
well as to simplify integration into systems
using systemd.</para>
command line argument, to ease debugging as
well as to simplify integration into systems
using systemd.</para>
for details.</para></listitem>
<listitem><para>As much as possible,
for details.</para></listitem>
<listitem><para>As much as possible,
- rely on the init systemd's
+ rely on the init system's
functionality to limit the access of
the daemon to files, services and
other resources. i.e. in the case of
functionality to limit the access of
the daemon to files, services and
other resources. i.e. in the case of
<para>New-style daemons which support socket
activation must be able to receive their
<para>New-style daemons which support socket
activation must be able to receive their
- sockets from the init system, instead of of
+ sockets from the init system, instead of
creating and binding them themselves. For
details about the programming interfaces for
this scheme provided by systemd see
creating and binding them themselves. For
details about the programming interfaces for
this scheme provided by systemd see
<listitem>
<para>Parameters understood by
the system and service manager
<listitem>
<para>Parameters understood by
the system and service manager
- to control system behaviour. For details see
+ to control system behavior. For details see
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
</listitem>
</varlistentry>
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
</listitem>
</varlistentry>
<varname>LC_TELEPHONE=</varname>,
<varname>LC_MEASUREMENT=</varname>,
<varname>LC_IDENTIFICATION=</varname>. Note that
<varname>LC_TELEPHONE=</varname>,
<varname>LC_MEASUREMENT=</varname>,
<varname>LC_IDENTIFICATION=</varname>. Note that
- <varname>LC_ALL</varname> may not be be configured in
+ <varname>LC_ALL</varname> may not be configured in
this file. For details about the meaning and semantics
of these settings, refer to
<citerefentry><refentrytitle>locale</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
this file. For details about the meaning and semantics
of these settings, refer to
<citerefentry><refentrytitle>locale</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
listed in this argument will not be
subject to the effect of
<option>kill-session-processes=</option>. Note
listed in this argument will not be
subject to the effect of
<option>kill-session-processes=</option>. Note
- that that this option takes precedence
+ that this option takes precedence
over
<option>kill-only-users=</option>, and
hence whatever is listed for
over
<option>kill-only-users=</option>, and
hence whatever is listed for
in again, the directory contents will
have been lost in between, but
applications should not rely on this
in again, the directory contents will
have been lost in between, but
applications should not rely on this
- behaviour and must be able to deal with
+ behavior and must be able to deal with
stale files. To store session-private
data in this directory the user should
include the value of <varname>$XDG_SESSION_ID</varname>
stale files. To store session-private
data in this directory the user should
include the value of <varname>$XDG_SESSION_ID</varname>
object of type <literal>va_list</literal> (see
<citerefentry><refentrytitle>stdarg</refentrytitle><manvolnum>3</manvolnum></citerefentry>
for more information) instead of the format string. It
object of type <literal>va_list</literal> (see
<citerefentry><refentrytitle>stdarg</refentrytitle><manvolnum>3</manvolnum></citerefentry>
for more information) instead of the format string. It
- is otherwise equivalent in behaviour.</para>
+ is otherwise equivalent in behavior.</para>
<para><function>sd_journal_send()</function> may be
used to submit structured log entries to the system
<para><function>sd_journal_send()</function> may be
used to submit structured log entries to the system
a seat, if there is any. Returns the session
identifier and the user identifier of the Unix user
the session is belonging to. Either the session or the
a seat, if there is any. Returns the session
identifier and the user identifier of the Unix user
the session is belonging to. Either the session or the
- user identifier parameter can be be passed NULL, in
+ user identifier parameter can be passed NULL, in
case only one of the parameters shall be queried. The
returned string needs to be freed with the libc
<citerefentry><refentrytitle>free</refentrytitle><manvolnum>3</manvolnum></citerefentry>
case only one of the parameters shall be queried. The
returned string needs to be freed with the libc
<citerefentry><refentrytitle>free</refentrytitle><manvolnum>3</manvolnum></citerefentry>
mounted read-only, immediately
followed by the system halt. If
<option>--force</option> is specified
mounted read-only, immediately
followed by the system halt. If
<option>--force</option> is specified
- twice the the operation is immediately
+ twice the operation is immediately
executed without terminating any
processes or unmounting any file
systems. This may result in data
executed without terminating any
processes or unmounting any file
systems. This may result in data
unmounted or mounted read-only,
immediately followed by the powering
off. If <option>--force</option> is
unmounted or mounted read-only,
immediately followed by the powering
off. If <option>--force</option> is
- specified twice the the operation is
+ specified twice the operation is
immediately executed without
terminating any processes or
unmounting any file systems. This may
immediately executed without
terminating any processes or
unmounting any file systems. This may
unmounted or mounted read-only,
immediately followed by the reboot. If
<option>--force</option> is specified
unmounted or mounted read-only,
immediately followed by the reboot. If
<option>--force</option> is specified
- twice the the operation is immediately
+ twice the operation is immediately
executed without terminating any
processes or unmounting any file
systems. This may result in data
executed without terminating any
processes or unmounting any file
systems. This may result in data
to 1 the device will be considered
plugged the moment it shows up in the
udev tree. This property has no
to 1 the device will be considered
plugged the moment it shows up in the
udev tree. This property has no
- influence on the behaviour when a
+ influence on the behavior when a
device disappears from the udev
tree. This option is useful to support
devices that initially show up in an
device disappears from the udev
tree. This option is useful to support
devices that initially show up in an
</varlistentry>
<varlistentry>
<term><varname>TTYVTDisallocate=</varname></term>
</varlistentry>
<varlistentry>
<term><varname>TTYVTDisallocate=</varname></term>
- <listitem><para>If the the terminal
+ <listitem><para>If the terminal
device specified with
<varname>TTYPath=</varname> is a
virtual console terminal try to
device specified with
<varname>TTYPath=</varname> is a
virtual console terminal try to
<listitem><para>Set a specific control
group attribute for executed
<listitem><para>Set a specific control
group attribute for executed
- processes, and (if needed) add the the
+ processes, and (if needed) add the
executed processes to a cgroup in the
hierarchy of the controller the
attribute belongs to. Takes two
executed processes to a cgroup in the
hierarchy of the controller the
attribute belongs to. Takes two
<varlistentry>
<term><varname>UtmpIdentifier=</varname></term>
<varlistentry>
<term><varname>UtmpIdentifier=</varname></term>
- <listitem><para>Takes a a four
+ <listitem><para>Takes a four
character identifier string for an
utmp/wtmp entry for this service. This
should only be set for services such
character identifier string for an
utmp/wtmp entry for this service. This
should only be set for services such
complete and all communication
channels set up. The child continues
to run as the main daemon
complete and all communication
channels set up. The child continues
to run as the main daemon
- process. This is the behaviour of
+ process. This is the behavior of
traditional UNIX daemons. If this
setting is used, it is recommended to
also use the
traditional UNIX daemons. If this
setting is used, it is recommended to
also use the
soon as the parent process
exits.</para>
soon as the parent process
exits.</para>
<option>oneshot</option> is similar
to <option>simple</option>, however
it is expected that the process has to
<option>oneshot</option> is similar
to <option>simple</option>, however
it is expected that the process has to
is particularly useful for this type
of service.</para>
is particularly useful for this type
of service.</para>
<option>dbus</option> is similar to
<option>simple</option>, however it is
expected that the daemon acquires a
<option>dbus</option> is similar to
<option>simple</option>, however it is
expected that the daemon acquires a
<varname>BusName=</varname> is
specified.</para>
<varname>BusName=</varname> is
specified.</para>
<option>notify</option> is similar to
<option>simple</option>, however it is
expected that the daemon sends a
<option>notify</option> is similar to
<option>simple</option>, however it is
expected that the daemon sends a
not set, it will be implicitly set to
<option>main</option>.</para>
not set, it will be implicitly set to
<option>main</option>.</para>
<option>idle</option> is very similar
to <option>simple</option>, however
actual execution of a the service
<option>idle</option> is very similar
to <option>simple</option>, however
actual execution of a the service
SIGTERM and SIGPIPE. Exit status
definitions can either be numeric exit
codes or termination signal names, and
SIGTERM and SIGPIPE. Exit status
definitions can either be numeric exit
codes or termination signal names, and
- are are separated by spaces. Example:
+ are separated by spaces. Example:
"<literal>SuccessExitStatus=1 2 8
SIGKILL</literal>", ensures that exit
codes 1, 2, 8 and the termination
"<literal>SuccessExitStatus=1 2 8
SIGKILL</literal>", ensures that exit
codes 1, 2, 8 and the termination
<listitem><para>Specifies a file
system FIFO to listen on. This expects
an absolute file system path as
<listitem><para>Specifies a file
system FIFO to listen on. This expects
an absolute file system path as
- argument. Behaviour otherwise is very
+ argument. Behavior otherwise is very
similar to the
<varname>ListenDatagram=</varname>
directive above.</para></listitem>
similar to the
<varname>ListenDatagram=</varname>
directive above.</para></listitem>
<listitem><para>Specifies a special
file in the file system to listen
on. This expects an absolute file
<listitem><para>Specifies a special
file in the file system to listen
on. This expects an absolute file
- system path as argument. Behaviour
+ system path as argument. Behavior
otherwise is very similar to the
<varname>ListenFIFO=</varname>
directive above. Use this to open
otherwise is very similar to the
<varname>ListenFIFO=</varname>
directive above. Use this to open
or <varname>kobject-uevent</varname>)
as argument, optionally suffixed by a
whitespace followed by a multicast
or <varname>kobject-uevent</varname>)
as argument, optionally suffixed by a
whitespace followed by a multicast
- group integer. Behaviour otherwise is
+ group integer. Behavior otherwise is
very similar to the
<varname>ListenDatagram=</varname>
directive above.</para></listitem>
very similar to the
<varname>ListenDatagram=</varname>
directive above.</para></listitem>
<listitem><para>Specifies a POSIX
message queue name to listen on. This
expects a valid message queue name
<listitem><para>Specifies a POSIX
message queue name to listen on. This
expects a valid message queue name
- (i.e. beginning with /). Behaviour
+ (i.e. beginning with /). Behavior
otherwise is very similar to the
<varname>ListenFIFO=</varname>
directive above. On Linux message
otherwise is very similar to the
<varname>ListenFIFO=</varname>
directive above. On Linux message
<listitem><para>Configures requirement
dependencies, very similar in style to
<varname>Requires=</varname>, however
<listitem><para>Configures requirement
dependencies, very similar in style to
<varname>Requires=</varname>, however
- in addition to this behaviour it also
+ in addition to this behavior it also
declares that this unit is stopped
when any of the units listed suddenly
disappears. Units can suddenly,
declares that this unit is stopped
when any of the units listed suddenly
disappears. Units can suddenly,
/* Send a properties changed signal. First for the
* specific type, then for the generic unit. The
* clients may rely on this order to get atomic
/* Send a properties changed signal. First for the
* specific type, then for the generic unit. The
* clients may rely on this order to get atomic
- * behaviour if needed. */
+ * behavior if needed. */
if (UNIT_VTABLE(u)->bus_invalidating_properties) {
if (UNIT_VTABLE(u)->bus_invalidating_properties) {
j->marker = from ? from : j;
j->generation = generation;
j->marker = from ? from : j;
j->generation = generation;
- /* We assume that the the dependencies are bidirectional, and
+ /* We assume that the dependencies are bidirectional, and
* hence can ignore UNIT_AFTER */
SET_FOREACH(u, j->unit->dependencies[UNIT_BEFORE], i) {
Job *o;
* hence can ignore UNIT_AFTER */
SET_FOREACH(u, j->unit->dependencies[UNIT_BEFORE], i) {
Job *o;
/* Note that this is called for all low-level state changes,
* even if they might map to the same high-level
* UnitActiveState! That means that ns == os is OK an expected
/* Note that this is called for all low-level state changes,
* even if they might map to the same high-level
* UnitActiveState! That means that ns == os is OK an expected
- * behaviour here. For example: if a mount point is remounted
+ * behavior here. For example: if a mount point is remounted
* this function will be called too! */
if (u->manager->n_reloading <= 0) {
* this function will be called too! */
if (u->manager->n_reloading <= 0) {
* UNIT_STUB if no configuration could be found. */
int (*load)(Unit *u);
* UNIT_STUB if no configuration could be found. */
int (*load)(Unit *u);
- /* If a a lot of units got created via enumerate(), this is
+ /* If a lot of units got created via enumerate(), this is
* where to actually set the state and call unit_notify(). */
int (*coldplug)(Unit *u);
* where to actually set the state and call unit_notify(). */
int (*coldplug)(Unit *u);
__sync_synchronize();
if (ftruncate(f->fd, f->last_stat.st_size) < 0)
__sync_synchronize();
if (ftruncate(f->fd, f->last_stat.st_size) < 0)
- log_error("Failed to to truncate file to its own size: %m");
+ log_error("Failed to truncate file to its own size: %m");
}
int journal_file_append_entry(JournalFile *f, const dual_timestamp *ts, const struct iovec iovec[], unsigned n_iovec, uint64_t *seqnum, Object **ret, uint64_t *offset) {
}
int journal_file_append_entry(JournalFile *f, const dual_timestamp *ts, const struct iovec iovec[], unsigned n_iovec, uint64_t *seqnum, Object **ret, uint64_t *offset) {
the public domain. It has no warranty.
You probably want to use hashlittle(). hashlittle() and hashbig()
the public domain. It has no warranty.
You probably want to use hashlittle(). hashlittle() and hashbig()
-hash byte arrays. hashlittle() is is faster than hashbig() on
+hash byte arrays. hashlittle() is faster than hashbig() on
little-endian machines. Intel and AMD are little-endian machines.
On second thought, you probably want hashlittle2(), which is identical to
hashlittle() except it returns two 32-bit hashes for the price of one.
little-endian machines. Intel and AMD are little-endian machines.
On second thought, you probably want hashlittle2(), which is identical to
hashlittle() except it returns two 32-bit hashes for the price of one.
if (st) {
/* Memory maps that are larger then the files
if (st) {
/* Memory maps that are larger then the files
- underneath have undefined behaviour. Hence, clamp
+ underneath have undefined behavior. Hence, clamp
things to the file size if we know it */
if (woffset >= (uint64_t) st->st_size)
things to the file size if we know it */
if (woffset >= (uint64_t) st->st_size)
*
* Get the instance number of the device.
*
*
* Get the instance number of the device.
*
- * Returns: the trailing number string of of the device name
+ * Returns: the trailing number string of the device name
**/
_public_ const char *udev_device_get_sysnum(struct udev_device *udev_device)
{
**/
_public_ const char *udev_device_get_sysnum(struct udev_device *udev_device)
{
}
if (systemd_fds(udev, &fd_ctrl, &fd_netlink) >= 0) {
}
if (systemd_fds(udev, &fd_ctrl, &fd_netlink) >= 0) {
- /* get control and netlink socket from from systemd */
+ /* get control and netlink socket from systemd */
udev_ctrl = udev_ctrl_new_from_fd(udev, fd_ctrl);
if (udev_ctrl == NULL) {
log_error("error taking over udev control socket");
udev_ctrl = udev_ctrl_new_from_fd(udev, fd_ctrl);
if (udev_ctrl == NULL) {
log_error("error taking over udev control socket");
# $1 = search only in subdirectory of /kernel/$1
# $2 = function to call with module name to filter.
# This function will be passed the full path to the module to test.
# $1 = search only in subdirectory of /kernel/$1
# $2 = function to call with module name to filter.
# This function will be passed the full path to the module to test.
-# The behaviour of this function can vary depending on whether $hostonly is set.
+# The behavior of this function can vary depending on whether $hostonly is set.
# If it is, we will only look at modules that are already in memory.
# If it is not, we will look at all kernel modules
# This function returns the full filenames of modules that match $1
# If it is, we will only look at modules that are already in memory.
# If it is not, we will look at all kernel modules
# This function returns the full filenames of modules that match $1
~ianmdlvl / elogind.git / commitdiff