about summary refs log tree commit diff
path: root/doc/s6-setlock.html
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2015-01-15 20:14:44 +0000
committerLaurent Bercot <ska-skaware@skarnet.org>2015-01-15 20:14:44 +0000
commit87c5b2118efcee65eeda3f743d081ea9c2b866d9 (patch)
tree31ca07d6134adf44bc3d58f4fcf4ea8be9cb7dbb /doc/s6-setlock.html
parentcd2500fcc704287c4994a3253b593593c867913e (diff)
downloads6-87c5b2118efcee65eeda3f743d081ea9c2b866d9.tar.gz
s6-87c5b2118efcee65eeda3f743d081ea9c2b866d9.tar.xz
s6-87c5b2118efcee65eeda3f743d081ea9c2b866d9.zip
Move Unix domain utilities and access control utilites,
as well as the accessrules library, from s6-networking to here
Diffstat (limited to 'doc/s6-setlock.html')
-rw-r--r--doc/s6-setlock.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/s6-setlock.html b/doc/s6-setlock.html
index f425656..f163336 100644
--- a/doc/s6-setlock.html
+++ b/doc/s6-setlock.html
@@ -55,7 +55,7 @@ execution. This is intended: the fd holds the lock, which is released
 when <em>prog</em> exits. <em>prog</em> must not touch fds it does not
 know about. </li>
  <li> If the timed lock option is chosen, s6-setlock does not acquire the lock
-itself. Instead, it spawns a <a href="libs6lock/s6lockd-helper.html">s6lockd-helper</a>
+itself. Instead, it spawns a <a href="libs6/s6lockd-helper.html">s6lockd-helper</a>
 process that acquires the lock while s6-setlock controls the timeout; the
 s6lockd-helper process then holds the lock and lives as long as
 <em>prog</em>. </li>