Date: Thu, 22 Feb 2001 23:10:16 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: mouss <usebsd@free.fr> Cc: diwil@eis.ru, freebsd-hackers@FreeBSD.ORG Subject: Re: warning in free(): Message-ID: <5152.982879816@critter> In-Reply-To: Your message of "Thu, 22 Feb 2001 16:45:42 %2B0100." <4.3.0.20010222164121.0594c510@pop.free.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <4.3.0.20010222164121.0594c510@pop.free.fr>, 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 phk@FreeBSD.ORG | 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 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?5152.982879816>