From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29417 invoked by alias); 17 Feb 2009 08:38:43 -0000 Received: (qmail 29389 invoked by uid 48); 17 Feb 2009 08:38:31 -0000 Date: Tue, 17 Feb 2009 08:38:00 -0000 Message-ID: <20090217083831.29386.qmail@sourceware.org> From: "walch dot martin at web dot de" To: glibc-bugs@sources.redhat.com In-Reply-To: <20090217003308.9854.walch.martin@web.de> References: <20090217003308.9854.walch.martin@web.de> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/9854] glibc opens up new tty to print *** %n in writable segment detected *** X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2009-02/txt/msg00058.txt.bz2 ------- Additional Comments From walch dot martin at web dot de 2009-02-17 08:38 ------- IMO the exact opposite is true. The message can not be logged and will be discarded. It will be ignored, because it will not even be recognized. It is always possible to ignore a warning, no matter how it is announced. But when caring about important warnings, they are expected on stderr. I personally prefer an operating system that cooperates and does not force me to keep a terminal open. -- http://sourceware.org/bugzilla/show_bug.cgi?id=9854 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.