summaryrefslogtreecommitdiff
path: root/man/systemd.path.xml
blob: 44f536cfccf41717d0310543984c69b3a29402c0 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
<?xml version='1.0'?> <!--*-nxml-*-->
<?xml-stylesheet type="text/xsl" href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"?>
<!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
  under the terms of the GNU General Public License as published by
  the Free Software Foundation; either version 2 of the License, or
  (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
  General Public License for more details.

  You should have received a copy of the GNU General Public License
  along with systemd; If not, see <http://www.gnu.org/licenses/>.
-->

<refentry id="systemd.path">
        <refentryinfo>
                <title>systemd.path</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>systemd.path</refentrytitle>
                <manvolnum>5</manvolnum>
        </refmeta>

        <refnamediv>
                <refname>systemd.path</refname>
                <refpurpose>systemd path configuration files</refpurpose>
        </refnamediv>

        <refsynopsisdiv>
                <para><filename>systemd.path</filename></para>
        </refsynopsisdiv>

        <refsect1>
                <title>Description</title>

                <para>A unit configuration file whose name ends in
                <filename>.path</filename> encodes information about
                a path monitored by systemd, for
                path-based activation.</para>

                <para>This man page lists the configuration options
                specific to this unit type. See
                <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
                for the common options of all unit configuration
                files. The common configuration items are configured
                in the generic [Unit] and [Install] sections. The
                path specific configuration options are configured in
                the [Path] section.</para>

                <para>For each path file a matching unit file must
                exist, describing the unit to activate when the path
                changes. By default a service by the same name as the
                path (except for the suffix) is activated. Example: a
                path file <filename>foo.path</filename> activates a
                matching service <filename>foo.service</filename>. The
                unit to activate may be controlled by
                <varname>Unit=</varname> (see below).</para>

                <para>Internally, path units use the
                <citerefentry><refentrytitle>inotify</refentrytitle><manvolnum>7</manvolnum></citerefentry>
                API to monitor file systems. Due to that it suffers by the
                same limitations as inotify, and for example cannot be
                used to monitor files or directories changed by other
                machines on remote NFS file systems.</para>

                <para>If an path unit is beneath another mount
                point in the file system hierarchy a dependency
                between both units is created automatically.</para>
        </refsect1>

        <refsect1>
                <title>Options</title>

                <para>Path files must include a [Path] section,
                which carries information about the path(s) it
                monitors. The options specific to the [Path] section
                of path units are the following:</para>

                <variablelist>
                        <varlistentry>
                                <term><varname>PathExists=</varname></term>
                                <term><varname>PathChanged=</varname></term>
                                <term><varname>DirectoryNotEmpty=</varname></term>

                                <listitem><para>Defines paths to
                                monitor for certain changes:
                                <varname>PathExists=</varname> may be
                                used to watch the mere existance of a
                                file or directory. If the file
                                specified exists the configured unit
                                is
                                activated. <varname>PathChanged=</varname>
                                may be used to watch a file or
                                directory and activate the configured
                                unit whenever it changes or is
                                modified. <varname>DirectoryNotEmpty=</varname>
                                may be used to watch a directory and
                                activate the configured unit whenver
                                it contains at least one file.</para>

                                <para>The arguments of these
                                directives must be absolute file
                                system paths.</para>

                                <para>Multiple directives may be
                                combined, of the same and of different
                                types, to watch multiple paths.</para>

                                <para>If a path is already existing
                                (in case of
                                <varname>PathExists=</varname>) or a
                                directory already is not empty (in
                                case of
                                <varname>DirectoryNotEmpty=</varname>)
                                at the time the path unit is activated
                                then the configured unit is
                                immediately activated as
                                well. Something similar does not apply
                                to <varname>PathChanged=</varname>.
                                </para></listitem>
                        </varlistentry>
                        <varlistentry>
                                <term><varname>Unit=</varname></term>

                                <listitem><para>The unit to activate
                                when any of the configured paths
                                changes. The argument is a unit name,
                                whose suffix is not
                                <filename>.path</filename>. If not
                                specified this value defaults to a
                                service that has the same name as the
                                path unit, except for the suffix. (See
                                above.) It is recommended that the
                                unit name that is activated and the
                                unit name of the path unit is chosen
                                identical except for the
                                suffix.</para></listitem>
                        </varlistentry>
                </variablelist>
        </refsect1>

        <refsect1>
                  <title>See Also</title>
                  <para>
                          <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
                          <citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
                          <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
                          <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
                          <citerefentry><refentrytitle>inotify</refentrytitle><manvolnum>7</manvolnum></citerefentry>
                  </para>
        </refsect1>

</refentry>