From owner-freebsd-ports-bugs@FreeBSD.ORG Tue Mar 16 05:10:16 2004 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6AF416A4CF for ; Tue, 16 Mar 2004 05:10:16 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85CE243D31 for ; Tue, 16 Mar 2004 05:10:16 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i2GDAGbv000793 for ; Tue, 16 Mar 2004 05:10:16 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i2GDAGDs000792; Tue, 16 Mar 2004 05:10:16 -0800 (PST) (envelope-from gnats) Resent-Date: Tue, 16 Mar 2004 05:10:16 -0800 (PST) Resent-Message-Id: <200403161310.i2GDAGDs000792@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-ports-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Csaba Molnar Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0497116A74B for ; Tue, 16 Mar 2004 05:03:49 -0800 (PST) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id F412943D1D for ; Tue, 16 Mar 2004 05:03:48 -0800 (PST) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.10/8.12.10) with ESMTP id i2GD3m72090836 for ; Tue, 16 Mar 2004 05:03:48 -0800 (PST) (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.10/8.12.10/Submit) id i2GD3mvA090835; Tue, 16 Mar 2004 05:03:48 -0800 (PST) (envelope-from nobody) Message-Id: <200403161303.i2GD3mvA090835@www.freebsd.org> Date: Tue, 16 Mar 2004 05:03:48 -0800 (PST) From: Csaba Molnar To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: ports/64338: amarok uses up all kern.maxfilesperproc X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2004 13:10:16 -0000 >Number: 64338 >Category: ports >Synopsis: amarok uses up all kern.maxfilesperproc >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Mar 16 05:10:16 PST 2004 >Closed-Date: >Last-Modified: >Originator: Csaba Molnar >Release: 5.2.1-RELEASE >Organization: >Environment: FreeBSD mcsaba.nek.sh.unideb.hu 5.2.1-RELEASE-p1 FreeBSD 5.2.1-RELEASE-p1 #2: Mon Mar 15 13:07:39 CET 2004 root@mcsaba.nek.sh.unideb.hu:/usr/obj/usr/src/sys/smokie i386 >Description: After starting up amarok, the kern.openfiles value begins to rise, until it reaches the maximum value (on my system, 9500). I choose the 'serious' severity, because this can lead to system freeze (recoverable by killing amarok), and a wide range of problems: for instance, it can prevent ipfw from creating new dynamic rules. This is how it looks like on my computer: << Mon Mar 15 03:19 PM>> >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: >>sysctl -a | grep openf kern.openfiles: 586 # this is the state before starting amarok << Mon Mar 15 03:19 PM>> >>sysctl -a | grep openf kern.openfiles: 610 # right after amarok is started << Mon Mar 15 03:20 PM>> >>sysctl -a | grep openf kern.openfiles: 834 << Mon Mar 15 03:21 PM>> >>sysctl -a | grep openf kern.openfiles: 984