From b8950a22980c85e7818b0f60897b4379ce24c520 Mon Sep 17 00:00:00 2001
From: Lorenzo Blasa <lblasa@meta.com>
Date: Fri, 22 Sep 2023 08:17:48 -0700
Subject: [PATCH] Kill with -9 flag

Summary: There are reports in which kill as is doesn't kill the process. Using the '-9' flag does, so update troubleshoot message.

Reviewed By: LukeDefeo

Differential Revision: D49537427

fbshipit-source-id: a062c92528589cecf0f41e1c344c5d0ae1c3345d
---
 desktop/flipper-server-client/src/FlipperServerClient.tsx | 2 +-
 desktop/flipper-ui-core/src/dispatcher/flipperServer.tsx  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/desktop/flipper-server-client/src/FlipperServerClient.tsx b/desktop/flipper-server-client/src/FlipperServerClient.tsx
index 0993bd0e7..2695a17e0 100644
--- a/desktop/flipper-server-client/src/FlipperServerClient.tsx
+++ b/desktop/flipper-server-client/src/FlipperServerClient.tsx
@@ -50,7 +50,7 @@ export function createFlipperServerWithSocket(
           new Error(
             `Failed to connect to the server in a timely manner.
              It may be unresponsive. Run the following from the terminal 
-             'sudo kill $(lsof -t -i :52342)' as to kill any existing running instance, if any.`,
+             'sudo kill -9 $(lsof -t -i :52342)' as to kill any existing running instance, if any.`,
           ),
         );
       }, CONNECTION_TIMEOUT);
diff --git a/desktop/flipper-ui-core/src/dispatcher/flipperServer.tsx b/desktop/flipper-ui-core/src/dispatcher/flipperServer.tsx
index 4e06d8808..da29ac660 100644
--- a/desktop/flipper-ui-core/src/dispatcher/flipperServer.tsx
+++ b/desktop/flipper-ui-core/src/dispatcher/flipperServer.tsx
@@ -210,7 +210,7 @@ function handeEADDRINUSE(errorMessage: string) {
         <br />
         <br />
         Please try to kill the offending process by running{' '}
-        <code>sudo kill $(lsof -ti:PORTNUMBER)</code> and restart flipper.
+        <code>sudo kill -9 $(lsof -ti:PORTNUMBER)</code> and restart flipper.
         <br />
         <br />
         {errorMessage}