From b36b082c8a24d2575909c3e0b4b8aeec49ec17bb Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 2 Jul 2010 02:38:30 +0200 Subject: man: document path units --- man/systemd.path.xml | 174 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 174 insertions(+) create mode 100644 man/systemd.path.xml (limited to 'man/systemd.path.xml') diff --git a/man/systemd.path.xml b/man/systemd.path.xml new file mode 100644 index 0000000000..44f536cfcc --- /dev/null +++ b/man/systemd.path.xml @@ -0,0 +1,174 @@ + + + + + + + + + systemd.path + systemd + + + + Developer + Lennart + Poettering + lennart@poettering.net + + + + + + systemd.path + 5 + + + + systemd.path + systemd path configuration files + + + + systemd.path + + + + Description + + A unit configuration file whose name ends in + .path encodes information about + a path monitored by systemd, for + path-based activation. + + This man page lists the configuration options + specific to this unit type. See + systemd.unit5 + 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. + + 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 foo.path activates a + matching service foo.service. The + unit to activate may be controlled by + Unit= (see below). + + Internally, path units use the + inotify7 + 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. + + If an path unit is beneath another mount + point in the file system hierarchy a dependency + between both units is created automatically. + + + + Options + + 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: + + + + PathExists= + PathChanged= + DirectoryNotEmpty= + + Defines paths to + monitor for certain changes: + PathExists= may be + used to watch the mere existance of a + file or directory. If the file + specified exists the configured unit + is + activated. PathChanged= + may be used to watch a file or + directory and activate the configured + unit whenever it changes or is + modified. DirectoryNotEmpty= + may be used to watch a directory and + activate the configured unit whenver + it contains at least one file. + + The arguments of these + directives must be absolute file + system paths. + + Multiple directives may be + combined, of the same and of different + types, to watch multiple paths. + + If a path is already existing + (in case of + PathExists=) or a + directory already is not empty (in + case of + DirectoryNotEmpty=) + at the time the path unit is activated + then the configured unit is + immediately activated as + well. Something similar does not apply + to PathChanged=. + + + + Unit= + + The unit to activate + when any of the configured paths + changes. The argument is a unit name, + whose suffix is not + .path. 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. + + + + + + See Also + + systemd8, + systemctl8, + systemd.unit5, + systemd.service5, + inotify7 + + + + -- cgit v1.2.3-54-g00ecf