From 7892d35c0b192ad16d07dee93cec88d7294f9b63 Mon Sep 17 00:00:00 2001 From: Matthew Leeds Date: Thu, 27 Sep 2018 18:29:30 -0700 Subject: [PATCH] lib/repo: Fix minor mistake in locking docs The config option is "lock-timeout-secs" not "lock-timeout". Closes: #1737 Approved by: jlebon --- src/libostree/ostree-repo.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/libostree/ostree-repo.c b/src/libostree/ostree-repo.c index 19f715aa..73ee027c 100644 --- a/src/libostree/ostree-repo.c +++ b/src/libostree/ostree-repo.c @@ -454,9 +454,9 @@ pop_repo_lock (OstreeRepo *self, * state is not changed and the stack is simply updated. * * ostree_repo_lock_push() waits for the lock depending on the repository's - * lock-timeout configuration. When lock-timeout is -1, a blocking lock is + * lock-timeout-secs configuration. When lock-timeout-secs is -1, a blocking lock is * attempted. Otherwise, the lock is taken non-blocking and - * ostree_repo_lock_push() will sleep synchronously up to lock-timeout seconds + * ostree_repo_lock_push() will sleep synchronously up to lock-timeout-secs seconds * attempting to acquire the lock. If the lock cannot be acquired within the * timeout, a %G_IO_ERROR_WOULD_BLOCK error is returned. * @@ -544,9 +544,9 @@ _ostree_repo_lock_push (OstreeRepo *self, * lock. * * ostree_repo_lock_pop() waits for the lock depending on the repository's - * lock-timeout configuration. When lock-timeout is -1, a blocking lock is + * lock-timeout-secs configuration. When lock-timeout-secs is -1, a blocking lock is * attempted. Otherwise, the lock is removed non-blocking and - * ostree_repo_lock_pop() will sleep synchronously up to lock-timeout seconds + * ostree_repo_lock_pop() will sleep synchronously up to lock-timeout-secs seconds * attempting to remove the lock. If the lock cannot be removed within the * timeout, a %G_IO_ERROR_WOULD_BLOCK error is returned. *