From owner-freebsd-hackers@FreeBSD.ORG  Wed Apr  2 15:16:41 2014
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D4CDAA2C;
 Wed,  2 Apr 2014 15:16:41 +0000 (UTC)
Received: from mail.tdx.com (mail.tdx.com [62.13.128.18])
 by mx1.freebsd.org (Postfix) with ESMTP id 7A5A0D62;
 Wed,  2 Apr 2014 15:16:41 +0000 (UTC)
Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251])
 (authenticated bits=0)
 by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id s32FGeQC099913
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Wed, 2 Apr 2014 16:16:40 +0100 (BST)
Date: Wed, 02 Apr 2014 16:16:39 +0100
From: Karl Pielorz <kpielorz_lst@tdx.co.uk>
To: Ian Lepore <ian@FreeBSD.org>
Subject: Re: Stuck CLOSED sockets / sshd / zombies...
Message-ID: <5AF977E21700940D62541596@Mail-PC.tdx.co.uk>
In-Reply-To: <1396449673.81853.264.camel@revolution.hippie.lan>
References: <3FE645E9723756F22EF901AE@Mail-PC.tdx.co.uk>
 <1396449673.81853.264.camel@revolution.hippie.lan>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: freebsd-hackers@FreeBSD.org
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 15:16:41 -0000



--On 02 April 2014 08:41 -0600 Ian Lepore <ian@FreeBSD.org> wrote:

> That may imply that adding "UsePrivilegeSeparation no" could be a
> workaround for anyone having severe problems with this on a production
> server, but it should in no way become mythology that doing this somehow
> "fixes" a problem -- it would be purely a workaround, and we should keep
> pursuing the actual problem.

Thanks for the reply,

I'll see if I can setup another system (same source/kernel etc.) - but with 
that option set, and see if that does indeed workaround the issue.

I'll leave the original system 'as-is' to run any further troubleshooting 
stuff against it.

-Karl