shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-23 21:35:11 +03:00
Code

man: document which condition tests follow symlinks

Browse Source 
ConditionPathExists and ConditionFileIsExecutable follow symlinks.
ConditionPathIsDirectory does not follow symlinks.
(XXX: is this actually the desired behavior?)
This commit is contained in:
Michal Schmidt 2011-09-20 12:28:22 +02:00
parent cbe8269481
commit 418112a296
1 changed files with 16 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
man/systemd.unit.xml
View File

@ -679,7 +679,7 @@
a file existence condition can be
checked before a unit is started. If
the specified absolute path name does
not exist startup of a unit will not
not exist, startup of a unit will not
actually happen, however the unit is
still useful for ordering purposes in
this case. The condition is checked at
@ -689,23 +689,22 @@
<varname>ConditionPathExists=</varname>
is prefixed with an exclamation mark
(!), the test is negated, and the unit
only started if the path does not
exist. <varname>ConditionPathExistsGlob=</varname>
work in a similar way, but checks for
the existance of at least one file or
is only started if the path does not
exist. The test follows symlinks.
<varname>ConditionPathExistsGlob=</varname>
works in a similar way, but checks for
the existence of at least one file or
directory matching the specified
globbing
pattern. <varname>ConditionPathIsDirectory=</varname>
is similar to
<varname>ConditionPathExists=</varname>
but verifies whether a certain path
exists and is a
directory. <varname>ConditionFileIsExecutable=</varname>
is similar to
<varname>ConditionPathExists=</varname>
but verifies whether a certain path
exists, is a regular file and marked
executable.
globbing pattern.
<varname>ConditionPathIsDirectory=</varname>
is similar to <varname>ConditionPathExists=</varname>
but verifies whether a certain path exists and
is a directory. It does not follow symlinks.
<varname>ConditionFileIsExecutable=</varname>
is similar to <varname>ConditionPathExists=</varname>
but verifies whether a certain path exists,
is a regular file and marked executable.
It follows symlinks.
<varname>ConditionDirectoryNotEmpty=</varname>
is similar to
<varname>ConditionPathExists=</varname>