In message <[EMAIL PROTECTED]>, mouss writes:
>Now having free() write to stdout/stderr isn't necessarily a good thing
>for daemons. If the message goes through a socket, it'll be hard to
>debug, which was the original intent.
>
>I suggest having some way so that when a program becomes a daemon,
>it can set some "silent-libc" or "libc messages go to logs" instead of
>using stdout/stderr.
Since some time ago, there is an API to control how the messages
from malloc is output, look for "malloc_message" in malloc(3).
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
