From owner-freebsd-current@FreeBSD.ORG Tue Aug 26 15:00:09 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B6B01065685 for ; Tue, 26 Aug 2008 15:00:09 +0000 (UTC) (envelope-from kevinxlinuz@163.com) Received: from m12-16.163.com (m12-16.163.com [220.181.12.16]) by mx1.freebsd.org (Postfix) with SMTP id A9B328FC2B for ; Tue, 26 Aug 2008 15:00:08 +0000 (UTC) (envelope-from kevinxlinuz@163.com) Received: from datastream-laptop.people.163.org (unknown [122.234.4.133]) by smtp12 (Coremail) with SMTP id EMCowLBbokztFrRIhJp1RA==.44464S2; Tue, 26 Aug 2008 22:45:02 +0800 (CST) Message-ID: <48B416E7.70905@163.com> Date: Tue, 26 Aug 2008 22:44:55 +0800 From: kevin User-Agent: Thunderbird 2.0.0.12 (X11/20080425) MIME-Version: 1.0 To: current@freebsd.org References: <20080826124335.GD3305@carrot.paeps.cx> In-Reply-To: <20080826124335.GD3305@carrot.paeps.cx> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Coremail-Antispam: 1Uf129KBjDUn29KB7ZKAUJUUUUUYxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUjVkYjsxI4VWxJwAYFVCjjxCrM7AC8VAFwI0_Jr0_Gr1l1I0E4x80 FVCIwcAKzIAtM7C26IkvcIIF6IxKo4kEV4yl1IIY67AEw4v_Jr0_Jr4ln4vEbcI7uVAqrc v_JFW8Xr15M2vj6xkI62vS6c8GOVWUtr1rJFyl5I8CrVACY4xI64kE6c02F40Ex7xfMcIj 6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67AKxVWUJVW8JwAC62BYpTIE1TZKA3svLV AKvSnIqfZI6r4lFVCF04k20xvEw2I207IF0wCjxxvEw4Wlc7Ca8VAvwVA2a4k0FcxrMxkI ecxEwVAFwVW5XwCY0x0Ix7I2Y4AK64vIr41l4x8a6c8ajcxJMI8E67AF67kF1VAFwI0_Jr 0_JrylIxAIcVC2z280aVAFwI0_Jr0_Gr1lIxAIcVC2z280aVCY1x0267AKxVWUJVW8JbIY CTnIWIevJa73UjIFyTuYvjxUqo7KDUUUU Cc: Subject: Re: Enormous utmp since mpsafetty X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Aug 2008 15:00:09 -0000 Philip Paeps wrote: > Has anyone else noticed that /var/run/utmp sometimes grows to insane sizes > (998M) since mpsafetty? I've been trying to pinpoint the culprit but I > haven't been successful so far. > > I don't think mpsafetty itself is to blame. Rather something which expects > our old tty system. > > My original reaction was to blame screen, but I can't immediately see where it > might be going wrong. > > Mysterious. Anyone have any ideas? > > - Philip > Could you check the output of `last`? Thanks, kevin