# How to make a lock using system.util.getGlobals()?

**URL:** <https://forum.inductiveautomation.com/t/how-to-make-a-lock-using-system-util-getglobals/96374>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [September 24, 2024, 2:31pm UTC](https://forum.inductiveautomation.com/t/how-to-make-a-lock-using-system-util-getglobals/96374 "2024-09-24T14:31:39Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 24, 2024, 3:13pm UTC](https://forum.inductiveautomation.com/t/how-to-make-a-lock-using-system-util-getglobals/96374/5 "2024-09-24T15:13:38Z")

</div>

This topic and its linked topics have additional guidance and examples:

> [@Understanding Synchronization and Data Access with system.util.getGlobals](https://forum.inductiveautomation.com/t/understanding-synchronization-and-data-access-with-system-util-getglobals/86019):
>
> Hello, I'm seeking insights on backing storage and synchronization primitives for data accessed via the [system-util-getGlobals function](https://www.docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-util/system-util-getGlobals#keywords). While it seems promising for my goals, I'm looking to better understand its underlying mechanisms to ensure correct implementation. Background I'm more experienced with Rust, so let me share a recent project as context. I had to manage mutable values maintained by their respective tasks running on threads within an asynchronous runtime, with a dedicated TUI t…

---

_[View the full topic](https://forum.inductiveautomation.com/t/how-to-make-a-lock-using-system-util-getglobals/96374)._