From: Ammar Faizi <[email protected]>
To: Arthur Lapz <[email protected]>
Cc: GNU/Weeb Mailing List <[email protected]>
Subject: Re: [PATCH] slc: Fix file descriptor leak
Date: Mon, 6 Jun 2022 09:46:40 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 6/6/22 9:42 AM, Arthur Lapz wrote:
> Unfortunately, this patch isn't a cure (still the same). :(
Not sure what is going on here, but the file descriptor bug
did really exist and is fixed by that patch.
The current SLC server looks like this:
The "lost client" has been connected!
fd_in is down
send: Connection reset by peer
send: Broken pipe
send: Broken pipe
send: Broken pipe
send: Broken pipe
send: Broken pipe
send: Broken pipe
send: Broken pipe
send: Broken pipe
send: Broken pipe
send: Broken pipe
send: Broken pipe
send: Broken pipe
send: Broken pipe
I will investigate it later after doing some work.
--
Ammar Faizi
next prev parent reply other threads:[~2022-06-06 2:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 2:27 [PATCH] slc: Fix file descriptor leak Ammar Faizi
2022-06-06 2:28 ` Ammar Faizi
2022-06-06 2:42 ` Arthur Lapz
2022-06-06 2:46 ` Ammar Faizi [this message]
2022-06-06 2:51 ` Ammar Faizi
2022-06-06 2:56 ` Arthur Lapz
2022-06-06 2:57 ` Ammar Faizi
2022-06-06 2:59 ` Arthur Lapz
2022-06-06 2:54 ` Alviro Iskandar Setiawan
2022-06-06 3:02 ` Ammar Faizi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox