Date: Tue, 6 May 2025 10:30:25 -0500 From: Kyle Evans <kevans@FreeBSD.org> To: Gleb Smirnoff <glebius@freebsd.org>, Cy Schubert <Cy.Schubert@cschubert.com> Cc: src-committers@freebsd.org, dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org Subject: Re: git: d15792780760 - main - unix: new implementation of unix/stream & unix/seqpacket Message-ID: <99f7c9ac-441b-43bc-b574-3bbb9c265a32@FreeBSD.org> In-Reply-To: <aBopyxs3FAqD6K4P@cell.glebi.us> References: <202505051956.545JuOPR085707@gitrepo.freebsd.org> <20250506150654.DEAF8300@slippy.cwsent.com> <aBopyxs3FAqD6K4P@cell.glebi.us>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/6/25 10:24, Gleb Smirnoff wrote: > On Tue, May 06, 2025 at 08:06:54AM -0700, Cy Schubert wrote: > C> Is anyone else experiencing rsync hangs with this? I'm noticing rsync hangs > C> with large files, like those in /usr/obj or a poudriere package repo. > C> > C> I haven't reverted this locally yet, just guessing ATM. > > Does rsync use unix(4) socket? What is the kernel stack of the sleeping > process? procstat -k $pid > rsync traditionally uses a SOCK_STREAM unix(4) socket constructed via socketpair(2). Thanks, Kyle Evans
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99f7c9ac-441b-43bc-b574-3bbb9c265a32>