Gentoo Archives: gentoo-user

From: Richard Fish <bigfish@××××××××××.org>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] pet peeve: sending normal output to stderr (env-update)
Date: Tue, 14 Nov 2006 20:51:12
Message-Id: 7573e9640611141245w456ee863yde01fdf8c268156@mail.gmail.com
In Reply to: [gentoo-user] pet peeve: sending normal output to stderr (env-update) by David Talkington
1 On 11/14/06, David Talkington <dtalk@××××××××××.org> wrote:
2 > -----BEGIN PGP SIGNED MESSAGE-----
3 > Hash: SHA1
4 >
5 >
6 > Why on earth does env-update send this:
7 >
8 > >>> Regenerating /etc/ld.so.cache...
9
10 env-update.sh outputs this message with a simple "echo", so no output
11 to stdout here. However portage writes most ">>>" messages to stderr.
12
13 You can either file a bug report on bugs.gentoo.org to try and get the
14 behavior changed, or use "emerge ... 2>&1 >/dev/null | grep -v -e '>>>
15 Regenerating '". This will send stdout to /dev/null, and stderr to
16 the pipe where grep can filter out whatever messages annoy you.
17
18 -Richard
19 --
20 gentoo-user@g.o mailing list

Replies

Subject Author
Re: [gentoo-user] [OT] pet peeve: sending normal output to stderr (env-update) Daniel Iliev <danny@××××××××.com>
[gentoo-user] Re: pet peeve: sending normal output to stderr (env-update) David Talkington <dtalk@××××××××××.org>