public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: Petr Baudis <pasky-AlSwsSmVLrQ@public.gmane.org>
Cc: "linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Ulrich Drepper <drepper-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: Review request: rtld-audit(7)
Date: Tue, 13 Jan 2009 13:22:29 +1300	[thread overview]
Message-ID: <496BDEC5.9070907@gmail.com> (raw)
In-Reply-To: <20090113170839.GD21648-DDGJ70k9y3lX+M3pkMnKjw@public.gmane.org>

Hi Petr 

Petr Baudis wrote:
>   Hi!
> 
>   I'm sorry, I won't have time to review the manpage in detail in the
> nearest future. :-( So three nits is all I can offer...

Thanks for taking a look anyway...

> On Mon, Jan 12, 2009 at 06:07:14PM +1300, Michael Kerrisk wrote:
>> .TH RTLD-AUDIT 7 2009-01-12 "Linux" "Linux Programmer's Manual"
>> .SH NAME
>> rtld-audit \- auditing API for the dynamic linker
>> .SH SYNOPSIS
>> .B #define _GNU_SOURCE
>>
>> .B #include <link.h>
>> .SH DESCRIPTION
>> The GNU dynamic linker (run-time linker)
> 
> The parentheses look awkward, is it necessary to have?

Better to have, IMO.

>> provides an auditing API that allows an application
>> to be notified when various dynamic linking events occur.
>> This API is very similar to the auditing interface provided by the
>> Solaris run-time linker.
> 
> So there _are_ differences? "compatible with", maybe?

Actually, I think "very similar" is probably better.  To me, "compatible"
implies something even closer to "they are the same".

>> The necessary constants and prototypes are defined by including
>> .IR <link.h> .
>>
>> To use this interface, the programmer creates a shared library
>> that implements a standard set of function names.
>> Not all of the functions need to be implemented: in most cases,
>> if the programmer is not interested in a particular class of auditing event,
>> then no implementation needs to be provided for the corresponding
>> auditing function.
>>
>> To employ the auditing interface, the environment variable
>> .BR LD_AUDIT
>> must be defined to contain a colon-separated list of shared libraries,
>> each of which can implement (parts of) the auditing API.
>> .\" FIXME Does specifying multiple audit libraries actually work
>> .\" on GNU?  My simple tests on Solaris work okay, but not on
>> .\" Linux -- mtk, Jan 2009
>> .\" glibc bug filed: http://sourceware.org/bugzilla/show_bug.cgi?id=9733
> 
> Make a BUGS section for this?

I'm still not 100% sure whether this is a bug in glibc, or a bug in my
understanding, so, I'm reluctant at this stage to write it up
in a BUGS section.

Cheers,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2009-01-13  0:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12  5:07 Review request: rtld-audit(7) Michael Kerrisk
     [not found] ` <cfd18e0f0901112107h4bfe3f64pa6e46136e2cc1e17-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-13 17:08   ` Petr Baudis
     [not found]     ` <20090113170839.GD21648-DDGJ70k9y3lX+M3pkMnKjw@public.gmane.org>
2009-01-13  0:22       ` Michael Kerrisk [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=496BDEC5.9070907@gmail.com \
    --to=mtk.manpages-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
    --cc=drepper-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pasky-AlSwsSmVLrQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox