| 1 |
Richard Fish wrote: |
| 2 |
> On 11/14/06, David Talkington <dtalk@××××××××××.org> wrote: |
| 3 |
>> -----BEGIN PGP SIGNED MESSAGE----- |
| 4 |
>> Hash: SHA1 |
| 5 |
>> |
| 6 |
>> |
| 7 |
>> Why on earth does env-update send this: |
| 8 |
>> |
| 9 |
>> >>> Regenerating /etc/ld.so.cache... |
| 10 |
> |
| 11 |
> env-update.sh outputs this message with a simple "echo", so no output |
| 12 |
> to stdout here. However portage writes most ">>>" messages to stderr. |
| 13 |
> |
| 14 |
> You can either file a bug report on bugs.gentoo.org to try and get the |
| 15 |
> behavior changed, or use "emerge ... 2>&1 >/dev/null | grep -v -e '>>> |
| 16 |
> Regenerating '". This will send stdout to /dev/null, and stderr to |
| 17 |
> the pipe where grep can filter out whatever messages annoy you. |
| 18 |
> |
| 19 |
> -Richard |
| 20 |
|
| 21 |
|
| 22 |
"emerge ... 2>&1 >/dev/null | grep -v -e '>>> Regenerating '" |
| 23 |
|
| 24 |
Isn't '>/dev/null' here by "typing habit" ? I think the right way is: |
| 25 |
|
| 26 |
command 2>&1 | grep... |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
Best regards, |
| 31 |
Daniel |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-user@g.o mailing list |
Archives