From 224b9c8a8aeeec8662c3fcbaa9a4ed62764cb4e9 Mon Sep 17 00:00:00 2001 From: BitwiseOperator Date: Mon, 14 Oct 2024 00:11:48 -0400 Subject: [PATCH] content-update --- ...x_Could_not_get_lock_Resource_temporarily_unavailable.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/Knowledge_Base/OS/Linux/Debian/Fixes/FIX_Linux_Could_not_get_lock_Resource_temporarily_unavailable.md b/docs/Knowledge_Base/OS/Linux/Debian/Fixes/FIX_Linux_Could_not_get_lock_Resource_temporarily_unavailable.md index 609473628..341505566 100644 --- a/docs/Knowledge_Base/OS/Linux/Debian/Fixes/FIX_Linux_Could_not_get_lock_Resource_temporarily_unavailable.md +++ b/docs/Knowledge_Base/OS/Linux/Debian/Fixes/FIX_Linux_Could_not_get_lock_Resource_temporarily_unavailable.md @@ -1,10 +1,12 @@ !!! info "" + If you are receiving the following error message, follow the steps below. + ![linux_lock_s987yn7hs](linux_lock_s987yn7hs.png) !!! warning "" - ### Method #1: Check for Running Processes + #### #1: Check for Running Processes ```bash ps aux | grep -i apt @@ -20,7 +22,7 @@ # from above picture PID is second col from left. PID is 7991 and 7993 [Yours will be different] ``` - ### Method #2: Remove Lock Files Manually + #### #2: Remove Lock Files Manually !!! warning ""