Date: Mon, 7 Oct 2002 09:53:00 -0700 (PDT) From: Tony Finch <fanf@FreeBSD.org> To: woerner@mediabase-gmbh.de, fanf@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/43739: cannot open file without obvious reason
| raw e-mail | index | archive | help
I am still a little bit upset due to Tony's funny analysis... I think a thorough analysis is necessary to maintain the advertised stability of FreeBSD. Simply rebooting is no solution in this sense. By the way: The system still suffers under my little test, although I hardly touched it since _one_ day and although there are only normal processes running (nearly all root), whilst the partner system (same hardware (but only 16MB main mem instead of 80MB main mem) same kernel same processes but no test victim) can do at least 13 'repeat...' commands (after the reboot (I did it some minutes ago) cyclops was able to do 13 'repeat...' commands without error, too): > ssh cyclops Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT-20020917-JPSNAP (RIDDICK) #0: Wed Sep 25 18:23:51 GMT 2002 Mit dem Kernel aus "Pitch Black"... > repeat 10 sh -c 'sleep 100 &' > repeat 10 sh -c 'sleep 100 &' Can't open /dev/null: Too many open files in system Can't open /dev/null: Too many open files in system Can't open /dev/null: Too many open files in system Can't open /dev/null: Too many open files in system Can't open /dev/null: Too many open files in system Can't open /dev/null: Too many open files in system Can't open /dev/null: Too many open files in system Can't open /dev/null: Too many open files in system I think the fact that the problem remains after one day of idle business is a clear hint that we have a bug here. I think further that it should be easy for experts like you to reproduce this bug. Of course I do not want to force you to enhance your product but I feel a little bit insulted because you wasted my time ... Thank you for your cooperation. -Arne To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message