Date: Wed, 26 Feb 1997 09:19:33 +0100 From: Poul-Henning Kamp <phk@critter.dk.tfs.com> To: Naoki Hamada <nao@sbl.cl.nec.co.jp> Cc: syssgm@devetir.qld.gov.au, j@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG Subject: Re: MALLOC(3) writes to stderr... Message-ID: <7995.856945173@critter.dk.tfs.com> In-Reply-To: Your message of "Wed, 26 Feb 1997 12:49:40 %2B0900." <199702260349.MAA00204@sirius.sbl.cl.nec.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199702260349.MAA00204@sirius.sbl.cl.nec.co.jp>, Naoki Hamada writes : >Stephen wrote: >>Although not enforced by the kernel, file descriptors 0, 1 and 2 have a >>conventional use that should always be respected. If you don't want to >>see stderr output, open /dev/null as descriptor 2. > >Thanks. I'm going to fix the daemon in this way. > >Also MALLOC(3) should be changed to keep silent unless explicitly >indicated, souldn't it? Malloc(3) would be in it's good right to simply coredump your process in any case where it will write to fd#2. It only does this after detected interface violations. I have considered adding a callback for reporting these kind of violations so that programs could register other handlers for it. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7995.856945173>