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_is_fifo" >
<refentryinfo >
<title > sd_is_fifo</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_is_fifo</refentrytitle>
<manvolnum > 3</manvolnum>
</refmeta>
<refnamediv >
<refname > sd_is_fifo</refname>
<refname > sd_is_socket</refname>
<refname > sd_is_socket_inet</refname>
<refname > sd_is_socket_unix</refname>
2011-05-17 21:37:03 +04:00
<refname > sd_is_mq</refname>
2013-11-07 20:51:09 +04:00
<refname > sd_is_special</refname>
2010-06-23 02:31:54 +04:00
<refpurpose > Check the type of a file descriptor</refpurpose>
</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_is_fifo</function> </funcdef>
<paramdef > int <parameter > fd</parameter> </paramdef>
<paramdef > const char *<parameter > path</parameter> </paramdef>
</funcprototype>
<funcprototype >
<funcdef > int <function > sd_is_socket</function> </funcdef>
<paramdef > int <parameter > fd</parameter> </paramdef>
<paramdef > int <parameter > family</parameter> </paramdef>
<paramdef > int <parameter > type</parameter> </paramdef>
<paramdef > int <parameter > listening</parameter> </paramdef>
</funcprototype>
<funcprototype >
<funcdef > int <function > sd_is_socket_inet</function> </funcdef>
<paramdef > int <parameter > fd</parameter> </paramdef>
<paramdef > int <parameter > family</parameter> </paramdef>
<paramdef > int <parameter > type</parameter> </paramdef>
<paramdef > int <parameter > listening</parameter> </paramdef>
<paramdef > uint16_t <parameter > port</parameter> </paramdef>
</funcprototype>
<funcprototype >
<funcdef > int <function > sd_is_socket_unix</function> </funcdef>
<paramdef > int <parameter > fd</parameter> </paramdef>
<paramdef > int <parameter > type</parameter> </paramdef>
<paramdef > int <parameter > listening</parameter> </paramdef>
<paramdef > const char* <parameter > path</parameter> </paramdef>
<paramdef > size_t <parameter > length</parameter> </paramdef>
</funcprototype>
2011-05-17 21:37:03 +04:00
<funcprototype >
<funcdef > int <function > sd_is_mq</function> </funcdef>
<paramdef > int <parameter > fd</parameter> </paramdef>
<paramdef > const char *<parameter > path</parameter> </paramdef>
</funcprototype>
2013-11-07 20:51:09 +04:00
<funcprototype >
<funcdef > int <function > sd_is_special</function> </funcdef>
<paramdef > int <parameter > fd</parameter> </paramdef>
<paramdef > const char *<parameter > path</parameter> </paramdef>
</funcprototype>
2010-06-23 02:31:54 +04:00
</funcsynopsis>
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
<para > <function > sd_is_fifo()</function> may be called
to check whether the specified file descriptor refers
2010-06-25 02:04:29 +04:00
to a FIFO or pipe. If the <parameter > path</parameter>
2013-06-29 20:09:14 +04:00
parameter is not <constant > NULL</constant> , it is
checked whether the FIFO is bound to the specified
file system path.</para>
2010-06-23 02:31:54 +04:00
<para > <function > sd_is_socket()</function> may be
called to check whether the specified file descriptor
2012-10-26 02:16:47 +04:00
refers to a socket. If the
2010-06-23 02:31:54 +04:00
<parameter > family</parameter> parameter is not
2013-06-27 23:51:44 +04:00
<constant > AF_UNSPEC</constant> , it is checked whether
2013-06-27 03:47:34 +04:00
the socket is of the specified family (AF_UNIX,
<constant > AF_INET</constant> , ...). If the
2013-06-27 23:51:44 +04:00
<parameter > type</parameter> parameter is not 0, it is
2010-06-23 02:31:54 +04:00
checked whether the socket is of the specified type
2013-06-27 03:47:34 +04:00
(<constant > SOCK_STREAM</constant> ,
<constant > SOCK_DGRAM</constant> , ...). If the
2013-06-27 23:51:44 +04:00
<parameter > listening</parameter> parameter is positive,
2010-06-23 02:31:54 +04:00
it is checked whether the socket is in accepting mode,
i.e. <function > listen()</function> has been called for
it. If <parameter > listening</parameter> is 0, it is
checked whether the socket is not in this mode. If the
parameter is negative, no such check is made. The
<parameter > listening</parameter> parameter should only
be used for stream sockets and should be set to a
negative value otherwise.</para>
<para > <function > sd_is_socket_inet()</function> is
similar to <function > sd_is_socket()</function> , but
optionally checks the IPv4 or IPv6 port number the
socket is bound to, unless <parameter > port</parameter>
is zero. For this call <parameter > family</parameter>
2013-06-27 03:47:34 +04:00
must be passed as either <constant > AF_UNSPEC</constant> , <constant > AF_INET</constant> , or
<constant > AF_INET6</constant> .</para>
2010-06-23 02:31:54 +04:00
<para > <function > sd_is_socket_unix()</function> is
2013-06-27 23:51:44 +04:00
similar to <function > sd_is_socket()</function> but
2013-06-27 03:47:34 +04:00
optionally checks the <constant > AF_UNIX</constant> path the socket is bound
2010-06-23 02:31:54 +04:00
to, unless the <parameter > path</parameter> parameter
2013-06-27 23:51:44 +04:00
is <constant > NULL</constant> . For normal file system <constant > AF_UNIX</constant> sockets,
set the <parameter > length</parameter> parameter to 0. For
Linux abstract namespace sockets, set the
2010-06-23 02:31:54 +04:00
<parameter > length</parameter> to the size of the
2013-06-27 23:51:44 +04:00
address, including the initial 0 byte, and set the
2010-06-23 02:31:54 +04:00
<parameter > path</parameter> to the initial 0 byte of
the socket address.</para>
2011-05-17 21:37:03 +04:00
<para > <function > sd_is_mq()</function> may be called to
check whether the specified file descriptor refers to
a POSIX message queue. If the
2013-06-29 20:09:14 +04:00
<parameter > path</parameter> parameter is not
<constant > NULL</constant> , it is checked whether the
message queue is bound to the specified name.</para>
2013-11-07 20:51:09 +04:00
<para > <function > sd_is_special()</function> may be
called to check whether the specified file descriptor
refers to a special file. If the
<parameter > path</parameter> parameter is not
<constant > NULL</constant> , it is checked whether file
descriptor is bound to the specified file
name. Special files in this context are character
device nodes and files in <filename > /proc</filename>
or <filename > /sys</filename> .</para>
2010-06-23 02:31:54 +04:00
</refsect1>
<refsect1 >
<title > Return Value</title>
<para > On failure, these calls return a negative
errno-style error code. If the file descriptor is of
2013-09-12 23:12:49 +04:00
the specified type and bound to the specified address,
2010-06-23 02:31:54 +04:00
a positive return value is returned, otherwise
zero.</para>
</refsect1>
<refsect1 >
<title > Notes</title>
<para > These functions are provided by the reference
implementation of APIs for new-style daemons and
distributed with the systemd package. The algorithms
2013-06-27 23:51:44 +04:00
they implement are simple, and they can easily be
2010-06-23 02:31:54 +04:00
reimplemented in daemons if it is important to support
this interface without using the reference
implementation.</para>
<para > Internally, these function use a combination of
<filename > fstat()</filename> and
<filename > getsockname()</filename> to check the file
descriptor type and where it is bound to.</para>
2013-06-27 23:51:44 +04:00
<para > For details about the algorithms, check the
2010-06-23 02:31:54 +04:00
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_is_fifo()</function> and the
related functions are implemented in the reference
2011-09-22 23:13:41 +04:00
implementation's <filename > sd-daemon.c</filename> and
<filename > sd-daemon.h</filename> files. These
interfaces are available as shared library, which can
be compiled and linked to with the
2013-06-27 20:38:15 +04:00
<constant > libsystemd-daemon</constant> <citerefentry > <refentrytitle > pkg-config</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
2011-09-22 23:13:41 +04:00
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>
2010-06-23 02:31:54 +04:00
<para > These functions continue to work as described,
even if -DDISABLE_SYSTEMD is set during
compilation.</para>
</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
<citerefentry > <refentrytitle > sd_listen_fds</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.service</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.socket</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
2010-06-25 02:04:29 +04:00
</para>
2010-06-23 02:31:54 +04:00
</refsect1>
</refentry>