From owner-freebsd-hackers Thu Feb 22 14:10:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (fw2.aub.dk [195.24.1.195]) by hub.freebsd.org (Postfix) with ESMTP id 3DFC637B401 for ; Thu, 22 Feb 2001 14:10:16 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f1MMAG505154; Thu, 22 Feb 2001 23:10:16 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: mouss Cc: diwil@eis.ru, freebsd-hackers@FreeBSD.ORG Subject: Re: warning in free(): In-Reply-To: Your message of "Thu, 22 Feb 2001 16:45:42 +0100." <4.3.0.20010222164121.0594c510@pop.free.fr> Date: Thu, 22 Feb 2001 23:10:16 +0100 Message-ID: <5152.982879816@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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