DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org EC1373858D32
MIME-Version: 1.0
References: <1277628349.20220822192219@yandex.ru>
In-Reply-To: <1277628349.20220822192219@yandex.ru>
From: "Stephen P. Carrier" <carrier@berkeley.edu>
Date: Tue, 23 Aug 2022 09:08:52 -0700
Message-ID: <CAKEdzNJQj78=ihd714MSNH5PkXP2GmRE74sBpB4PWLt26oqa6w@mail.gmail.com>
Subject: Re: Find out a process that holding the socket?
To: cygwin@cygwin.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

The 'handle' utility from Sysinternals should be able to help.
http://technet.microsoft.com/en-us/sysinternals/bb842062

--Stephen Carrier
  BEAR Center

On Mon, Aug 22, 2022 at 9:35 AM Andrey Repin <anrdaemon@yandex.ru> wrote:

> Greetings, All!
>
> I'm trying to write a small helper utility, and I need to find out, which
> process is holding a particular socket open.
> Since there's no "lsof" utility in Cygwin, which is commonly suggested for
> this task on Linux, I'm failing to find an alternative.
> Is there a simple solution available or I have to dig down into WinAPI?
> The process is going to run elevated, if that matters.
>
>
> --
> With best regards,
> Andrey Repin
> Monday, August 22, 2022 19:15:48
>
> Sorry for my terrible english...
>
>
> --
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
>

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple