This looks much more like a syslog/audit/... mechanism, and not really much like keven, which is about applications getting event notification on system objects. You might be interested in talking to Andrew Reiter <[EMAIL PROTECTED]> about his work on the TrustedBSD audit framework, but otherwise I'm not really sure we have something like this in the works right now.
Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services On Fri, 10 May 2002, Ramkumar Chinchani wrote: > > I am asking more in terms of the posix event logging mechanism being > implemented in Linux 2.5.x kernel. > > http://evlog.sourceforge.net/ > > How does the kevent mechanism of event notification and handling compare > to this scheme? > > It appears to me that the Linux event logging merely supports logging of > events in a different way that already exists via klogd. This is a more > passive technique and requiring disk usage overheads in case of huge and > rapid audits. > > On the other hand, kevent allows more active event registering and > handling... > > What would be the pros and cons of both these techniques? > > Thanks. > > -Ram > > ==> Terry Lambert <[EMAIL PROTECTED]>/11:23pm/May 9, 2002 <== > > [Ramkumar Chinchani wrote: > [> Has the POSIX event standard implemeted in FreeBSD? POSIX events are logged to > [> a file. Which would give a better performance, assuming kevent can register more > [> events? > [ > [Are you talking about POSIX persistent queueing, of the type not > [implemented by the POSIX printing model, based on Palladium out > [of Project Athena? > [ > [THat's more like a "Tuxedo" replacement, than anything else. It's > [not really comparable to kevent (IMO). > [ > [If you meant something else, you might want to ask a clearer question > [(i.e. give the standards information for the "event standard" you > [are talking about; there are so many to choose from, e.g. queued > [signal delivery, etc.). > [ > [-- Terry > [ > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
