From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 26 15:06:34 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 72985106; Fri, 26 Sep 2014 15:06:34 +0000 (UTC) Received: from mail.beastielabs.net (unknown [IPv6:2001:888:1227:0:200:24ff:fec9:5934]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 91BB090E; Fri, 26 Sep 2014 15:06:33 +0000 (UTC) Received: from beastie.hotsoft.nl (beastie.hotsoft.nl [IPv6:2001:888:1227:0:219:d1ff:fee8:91eb]) by mail.beastielabs.net (8.14.7/8.14.7) with ESMTP id s8QF6Umc067783; Fri, 26 Sep 2014 17:06:30 +0200 (CEST) (envelope-from hans@beastielabs.net) Message-ID: <542580F6.7030609@beastielabs.net> Date: Fri, 26 Sep 2014 17:06:30 +0200 From: Hans Ottevanger User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: =?UTF-8?B?RWR3YXJkIFRvbWFzeiBOYXBpZXJhxYJh?= Subject: Re: Fwd: Autofs: spurious (?) log messages and zombies from automountd References: <54226E4D.1040704@beastielabs.net> <54250A50.1000607@beastielabs.net> <20140926090053.GA10644@brick.home> <542540BB.80001@beastielabs.net> In-Reply-To: <542540BB.80001@beastielabs.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2014 15:06:34 -0000 On 09/26/14 12:32, Hans Ottevanger wrote: > On 09/26/14 11:00, Edward Tomasz NapieraƂa wrote: >> On 0926T0840, Hans Ottevanger wrote: [...] > > I planned to make a new CURRENT snapshot installation on another machine > anyhow today. I will see what happens there. > I just verified that with fresh installations of both 10.1-BETA2 and the latest CURRENT snapshot (based on r271779) the same issue occurs. Kind regards, Hans