Date: Tue, 16 Mar 2004 05:03:48 -0800 (PST) From: Csaba Molnar <molnarcs@message.hu> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/64338: amarok uses up all kern.maxfilesperproc Message-ID: <200403161303.i2GD3mvA090835@www.freebsd.org> Resent-Message-ID: <200403161310.i2GDAGDs000792@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403161303.i2GD3mvA090835>