Skip to contentSkip to conversation

tools: env: update lock path in README

PATCH In review John Keeping 3 participants 3 messages Apr 12, 2023 – Apr 26, 2023

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 tools: env: update lock path in README

Commit aeb40f1166 ("tools: env: use /run to store lockfile") updated the path to the lockfile but did not update the documentation to match.

Use the new path in the documentation.

Fixes aeb40f1166 ("tools: env: use /run to store lockfile")
---
 tools/env/README | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
tools/env/README +1 -1
index 709251383c..480a893202 100644
@@ -59,5 +59,5 @@ this environment instance. On NAND this is used to limit the range
 within which bad blocks are skipped, on NOR it is not used.
 
 To prevent losing changes to the environment and to prevent confusing the MTD
-drivers, a lock file at /var/lock/fw_printenv.lock is used to serialize access
+drivers, a lock file at /run/fw_printenv.lock is used to serialize access
 to the environment.
Signature · 1 line
2.40.0
Reviewed-by on v1 1/1
#1 lore raw
Quoted 11 lines · John Keeping

Commit aeb40f1166 ("tools: env: use /run to store lockfile") updated the path to the lockfile but did not update the documentation to match.

Use the new path in the documentation.

Fixes aeb40f1166 ("tools: env: use /run to store lockfile")
---
 tools/env/README | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)