From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Riedy Date: Fri, 11 Apr 2003 23:25:55 +0000 Subject: Re: [ANNOUNCE] udev 0.1 release Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org And Greg KH writes: - - But how many events to we buffer? When do we start to throw them away? - Fun policy decisions that we don't have to worry about in the current - scheme. Last time I checked, there was a limit on the number of running processes. What happens when the executable named in /proc/sys/kernel/hotplug fails to spawn? Looks like the events get dropped on the floor right now regardless of the reason why it failed to execve. I tend to prefer explicit decisions over implicit ones. It seems that the current system will lose track of events in the face of fork-bombs with no notification. An event system could insert one last "overflow" event into a queue when it's one short of full. (BTW, there seems to be code in sysfs to handle dnotify, and the rest is inherited through vfs, right? I don't have the hardware handy to test.) Jason ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel