Date: Fri, 1 Jan 2038 07:02:42 +0000 From: Niall Smart <rotel@indigo.ie> To: "Eric A. Davis" <edavis@nas.nasa.gov>, Eivind Eklund <eivind@yes.no> Cc: edavis@shark.nas.nasa.gov, freebsd-hackers@FreeBSD.ORG Subject: Re: how to add new system calls... Message-ID: <203801010702.HAA06275@indigo.ie> In-Reply-To: "Eric A. Davis" <edavis@nas.nasa.gov> "Re: how to add new system calls..." (Apr 15, 10:12am)
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 15, 10:12am, "Eric A. Davis" wrote: } Subject: Re: how to add new system calls... > Any other ideas would be great. I believe Windows NT has the ability to turn on/off auditing on a per file basis. It would be nice if you could provide for getting details like the uid who opened the file, a timestamp, open flags, denied open requests and other miscellaneous details like that if possible so someone later can write fauditlogd. (file audit log daemon) I wouldn't personally find it useful, but I'm sure someone else would. (And I can't resist suggesting ideas for others to implement ;)) It would be nice to be able to put in wildcard ``callbacks'' too, although perhaps this would introduce too much of a performance penalty. Do you have any idea how much overhead the system would have on normal files for which no ``callbacks'' have been installed? Sounds pretty cool. Niall -- Niall Smart. finger njs3@doc.ic.ac.uk for PGP key FreeBSD: Turning PC's into Workstations. www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?203801010702.HAA06275>