From owner-freebsd-hackers Thu Jan 27 23:40:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pacman.redwoodsoft.com (adsl-63-193-215-238.dsl.snfc21.pacbell.net [63.193.215.238]) by hub.freebsd.org (Postfix) with SMTP id A201D15A76 for ; Thu, 27 Jan 2000 23:40:19 -0800 (PST) (envelope-from dru@redwoodsoft.com) Received: (qmail 16023 invoked from network); 28 Jan 2000 07:40:12 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 28 Jan 2000 07:40:12 -0000 Date: Thu, 27 Jan 2000 23:40:12 -0800 (PST) From: Dru Nelson To: freebsd-hackers@freebsd.org Subject: Proper Kernel notification to a user level process In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is the proper or best practice method for the kernel to notify a user level process (or processes) of an event. This event may possibly have data. The processes may or may not exist. The event is generated by some arbitrary kernel event (a counter, a call being made, etc.) Typically I have seen this done as file I/O via a device. syslogd is a program that fits this description. A special device '/dev/klog' was provided for it. What is the best practice these days? Please reply to me directly, I will summarize the results to the list. Dru Nelson San Mateo, California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message