From owner-freebsd-net@FreeBSD.ORG Tue Mar 25 17:09:50 2014 Return-Path: Delivered-To: freebsd-net@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 2B5BA956 for ; Tue, 25 Mar 2014 17:09:50 +0000 (UTC) Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 04E7481B for ; Tue, 25 Mar 2014 17:09:49 +0000 (UTC) Received: by mail-pb0-f45.google.com with SMTP id uo5so724418pbc.18 for ; Tue, 25 Mar 2014 10:09:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=//iSyKJpTVah8I5RNmlZ9AXDdaYAXialOiZ0ehmf4j8=; b=No46yPoSOhDDIALS2pFKHy3BmfFzteqvzgtRT2CAemINhR+8NVI/WU2JiOlnWSUYXW OmEBVo8h9TnUX1X7ihthlensTNwgRX/Ei/oPN43RqcbjCH7joziMa1JCU1O22yx9qQAS rvTf7YRovnGU488KbIG4D5isy8QMyo1q3CZ8DooO7Sx6tTV2OmxsWd7mTKTVCyMVE839 e1VhSa1xor68yEV5N+5Hvu947sXp6XY4kx8g4cMM727a2ZLIJaGcPcUVC2MWkeshBl4m XyQrWsU3t/ORJ5PsTRM3qPVXuI/U3YTzwrx3GfQhxc1ya7wPbq/iLBIenCyxnBsDMvOK f5sQ== MIME-Version: 1.0 X-Received: by 10.68.250.3 with SMTP id yy3mr79980149pbc.56.1395767389697; Tue, 25 Mar 2014 10:09:49 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.66.0.164 with HTTP; Tue, 25 Mar 2014 10:09:49 -0700 (PDT) Date: Tue, 25 Mar 2014 10:09:49 -0700 X-Google-Sender-Auth: h_NhiNdYXGG6pQg8Autxj09ipYM Message-ID: Subject: Server sockets staying in CLOSED for extended periods From: Kevin Oberman To: "freebsd-net@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Mar 2014 17:09:50 -0000 There has been a long thread on stable about sshd processes being hung due to sockets remaining in a CLOSED state for extended periods in 10-stable. This did not seem to be happening with 9.2. (Not sure about 10.0.) Was here a change in the network stack on 10 that would have kept CLOSED sockets around for extended intervals? Should sshd processes hang for extended periods (forever?) unless killed (KILL)? I also wonder if a daemon process should refuse to exit if a closed socket remains. Any suggestions would help. the full thread with a great deal of detail is in stable with the subject "sshd with zombie process on FreeBSD 10.0-STABLE - workaround". -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com