summaryrefslogtreecommitdiff
path: root/util
diff options
context:
space:
mode:
authorDavid Hendricks <dhendrix@chromium.org>2016-03-02 12:39:44 -0800
committerchrome-bot <chrome-bot@chromium.org>2016-03-02 18:03:45 -0800
commitad7d6516b5dc041f9d2b1947dd550a592db09e0c (patch)
treea5c7dfe12fd417831cda15c5bd951d2498091220 /util
parent325fe5ac6079e28d21d78de75c3151db10614ebd (diff)
downloadchrome-ec-ad7d6516b5dc041f9d2b1947dd550a592db09e0c.tar.gz
locks: Update lockfile dir to be FHS 3.0 compliant
The Filesystem Hierarchy Standard version 3.0* specifies that /run should be used for runtime variables such as locks. The rationale for switching to use /run instead of /var/run was because /var might not be available at early boot. Since /run is implemented as a tmpfs and doesn't require /var to be mounted first it can be made available earlier. *http://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s15.html BUG=chromium:591366 BRANCH=none TEST=none Change-Id: Ic0b5ff336c1c258db8891c0a17c836497d9793c5 Signed-off-by: David Hendricks <dhendrix@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/330123 Reviewed-by: Shawn N <shawnn@chromium.org>
Diffstat (limited to 'util')
-rw-r--r--util/lock/locks.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/util/lock/locks.h b/util/lock/locks.h
index e87c36d73b..6875d91454 100644
--- a/util/lock/locks.h
+++ b/util/lock/locks.h
@@ -31,7 +31,7 @@
#ifndef __UTIL_LOCKS_H
#define __UTIL_LOCKS_H
-#define SYSTEM_LOCKFILE_DIR "/var/run/lock"
+#define SYSTEM_LOCKFILE_DIR "/run/lock"
#define LOCKFILE_NAME "firmware_utility_lock"
#define CROS_EC_LOCKFILE_NAME "cros_ec_lock"