Bug Hunter wrote:
> Thanks! I knew it was in the kernel. since it allows a (0) parameter,
> I was hoping that it was in a library somewhere. Really hoping.
The kernel doesn't use any libraries, and the kernel's functions
aren't callable by applications.
If you want to send a signal to a process, use kill() or killpg().
> I had earlier found all kinds of documentation in /usr/doc that said, in
> effect "This is a library!".
>
> Can you give me a hint where a compendium of the functions I expect to
> find in the various libraries on the system will be?
ls /usr/{,local/,X11/}man/man3 /usr/man/man2
will provide a fairly complete list.
> Or a pointer to an
> executable that will print out the functions a library exports?
The `nm' program will list all external symbols in an executable,
library or object file.
> Many times I have compiled programs only to find they
> need a function, and no library I can find on the net appears to have that
> function. When I post questions about the functions not found, the answer
> I get back is "it is in library xxyyzz". Usually, library xxyyzz does not
> exist. It is part of another larger library zzyyxx which is not
> documented, or is "so well known" that everyone knows it (except me).
> Or it has been renamed.
In general, the function should be documented in a manual page. The
manual page should provide some clue as to where the function comes
from. Also, some libraries adopt particular naming conventions (e.g.
Xlib functions begin with `X', X toolkit (Xt) functions begin with
`Xt' etc).
--
Glynn Clements <[EMAIL PROTECTED]>
