2010-06-23 02:31:54 +04:00
<?xml version='1.0'?> <!-- * - nxml - * -->
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<!--
This file is part of systemd.
Copyright 2010 Lennart Poettering
systemd is free software; you can redistribute it and/or modify it
2012-04-12 02:20:58 +04:00
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or
2010-06-23 02:31:54 +04:00
(at your option) any later version.
systemd is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
2012-04-12 02:20:58 +04:00
Lesser General Public License for more details.
2010-06-23 02:31:54 +04:00
2012-04-12 02:20:58 +04:00
You should have received a copy of the GNU Lesser General Public License
2010-06-23 02:31:54 +04:00
along with systemd; If not, see <http: / / w w w . g n u . o r g / l i c e n s e s /> .
-->
<refentry id= "sd_booted" >
<refentryinfo >
<title > sd_booted</title>
<productname > systemd</productname>
<authorgroup >
<author >
<contrib > Developer</contrib>
<firstname > Lennart</firstname>
<surname > Poettering</surname>
<email > lennart@poettering.net</email>
</author>
</authorgroup>
</refentryinfo>
<refmeta >
<refentrytitle > sd_booted</refentrytitle>
<manvolnum > 3</manvolnum>
</refmeta>
<refnamediv >
<refname > sd_booted</refname>
2012-07-16 20:08:25 +04:00
<refpurpose > Test whether the system is running the systemd init system</refpurpose>
2010-06-23 02:31:54 +04:00
</refnamediv>
<refsynopsisdiv >
<funcsynopsis >
2011-12-19 16:11:42 +04:00
<funcsynopsisinfo > #include < systemd/sd-daemon.h> </funcsynopsisinfo>
2010-06-23 02:31:54 +04:00
<funcprototype >
<funcdef > int <function > sd_booted</function> </funcdef>
<paramdef > void</paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
<para > <function > sd_booted()</function> checks whether
the system was booted up using the systemd init system.</para>
</refsect1>
<refsect1 >
<title > Return Value</title>
<para > On failure, this call returns a negative
errno-style error code. If the system was booted up
2010-06-25 02:04:29 +04:00
with systemd as init system, this call returns a
2010-06-24 19:25:16 +04:00
positive return value, zero otherwise.</para>
2010-06-23 02:31:54 +04:00
</refsect1>
<refsect1 >
<title > Notes</title>
<para > This function is provided by the reference
implementation of APIs for new-style daemons and
distributed with the systemd package. The algorithm it
implements is simple, and can easily be reimplemented
in daemons if it is important to support this
interface without using the reference
implementation.</para>
<para > Internally, this function checks whether the
sd-booted: update sd_booted() check a bit
Previously we were testing whether /sys/fs/cgroup/systemd/ was a mount
point. This might be problematic however, when the cgroup trees are bind
mounted into a container from the host (which should be absolutely
valid), which might create the impression that the container was running
systemd, but only the host actually is.
Replace this by a check for the existance of the directory
/run/systemd/system/, which should work unconditionally, since /run can
never be a bind mount but *must* be a tmpfs on systemd systems, which is
flushed at boots. This means that data in /run always reflects
information about the current boot, and only of the local container,
which makes it the perfect choice for a check like this.
(As side effect this is nice to Ubuntu people who now use logind with
the systemd cgroup hierarchy, where the old sd_booted() check misdetects
systemd, even though they still run legacy Upstart.)
2013-03-15 19:41:40 +04:00
directory <filename > /run/systemd/system/</filename>
exists. A simple check like this can also be
implemented trivially in shell or any other
language.</para>
2010-06-23 02:31:54 +04:00
<para > For details about the algorithm check the
liberally licensed reference implementation sources:
2012-09-13 21:44:47 +04:00
<ulink url= "http://cgit.freedesktop.org/systemd/systemd/plain/src/libsystemd-daemon/sd-daemon.c" />
Reword sentences that contain psuedo-English "resp."
As you likely know, Arch Linux is in the process of moving to systemd.
So I was reading through the various systemd docs and quickly became
baffled by this new abbreviation "resp.", which I've never seen before
in my English-mother-tongue life.
Some quick Googling turned up a reference:
<http://www.transblawg.eu/index.php?/archives/870-Resp.-and-other-non-existent-English-wordsNicht-existente-englische-Woerter.html>
I guess it's a literal translation of the German "Beziehungsweise", but
English doesn't work the same way. The word "respectively" is used
exclusively to provide an ordering connection between two lists. E.g.
"the prefixes k, M, and G refer to kilo-, mega-, and giga-,
respectively." It is also never abbreviated to "resp." So the sentence
"Sets the default output resp. error output for all services and
sockets" makes no sense to a natural English speaker.
This patch removes all instances of "resp." in the man pages and
replaces them with sentences which are much more clear and, hopefully,
grammatically valid. In almost all instances, it was simply replacing
"resp." with "or," which the original author (Lennart?) could probably
just do in the future.
The only other instances of "resp." are in the src/ subtree, which I
don't feel privileged to correct.
Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>
2012-10-15 22:59:12 +04:00
and <ulink
2012-02-13 20:46:46 +04:00
url="http://cgit.freedesktop.org/systemd/systemd/plain/src/systemd/sd-daemon.h"/></para>
2010-06-23 02:31:54 +04:00
<para > <function > sd_booted()</function> is implemented
2011-09-22 23:13:41 +04:00
in the reference implementation's
2010-06-23 02:31:54 +04:00
<filename > sd-daemon.c</filename> and
2011-09-22 23:13:41 +04:00
<filename > sd-daemon.h</filename> files. These
interfaces are available as shared library, which can
be compiled and linked to with the
<literal > libsystemd-daemon</literal>
<citerefentry > <refentrytitle > pkg-config</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
file. Alternatively, applications consuming these APIs
may copy the implementation into their source
tree. For more details about the reference
implementation see
2012-07-13 03:50:05 +04:00
<citerefentry > <refentrytitle > sd-daemon</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> .</para>
2011-09-22 23:13:41 +04:00
<para > If the reference implementation is used as
drop-in files and -DDISABLE_SYSTEMD is set during
compilation this function will always return 0 and
otherwise become a NOP.</para>
2010-06-23 02:31:54 +04:00
</refsect1>
<refsect1 >
<title > See Also</title>
<para >
2010-06-24 02:11:04 +04:00
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
2012-07-13 03:50:05 +04:00
<citerefentry > <refentrytitle > sd-daemon</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry>
2010-06-23 02:31:54 +04:00
</para>
</refsect1>
</refentry>