ports/64338: amarok uses up all kern.maxfilesperproc
Csaba Molnar
molnarcs at message.hu
Tue Mar 16 13:10:16 UTC 2004
>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 at 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
More information about the freebsd-ports-bugs
mailing list