Bug 73087 – app-portage/esearch: non-error output of esync should go to stdout

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Andre Kloth 2004-12-01 16:05:47 UTC]

I'm running esync instead of emerge sync every night as a cron job:

  "0 6 * * *       /usr/sbin/esync > /dev/null"

Unfortunately i get every day an email with the standard output of esync.

David, could you please change this in you implementation or make an additional command line option like "--quiet"?

Thanks in advance.

Reproducible: Always
Steps to Reproduce:
esync > /dev/null
Actual Results:  
e.g.:

]2;Importing old portage tree]2;Doing '/usr/bin/emerge sync' now]2;Doing
'eupdatedb' now]2;Importing new portage tree]2;Preparing
databases]2;Searching for changes

Expected Results:  
Only error messages :)

[Comment 1 David Peter 2004-12-04 01:37:24 UTC]

This is strange,
I cannot reproduce this error (with esearch-0.7 / python 2.3.4).
Which version of esearch and python are you using?

In fact, I'm simply using 'print' for all my messages, so they normally
should go to stdout. Maybe there is something wrong with your python
config?
But even though, this bug report made me discover, that I also output
error messages with 'print', I'll change this in the next version.

What else could make python use stderr instead of stdout?

By the way.. if you use esync just for doing 'emerge sync' and 'eupdatedb', you should maybe use 'emerge sync && eupdatedb -q', because you don't need the output of esync then, right? => save time ;-)

[Comment 2 Andre Kloth 2004-12-06 19:29:11 UTC]

Same versions of esearch and python here. I can't find any configs for python :-|

But thanks for your useful hint - i'll adjust my crontab now :-)

[Comment 3 Alec Warner (RETIRED) 2006-04-24 10:36:35 UTC]

From the docs:
"""
Standard output is defined as the file object named stdout in the built-in module sys. If no such object exists, or if it does not have a write() method, a RuntimeError exception is raised.
"""

I'll take a look at this tonight.

[Comment 4 Paul Varner (RETIRED) 2009-01-02 20:05:57 UTC]

I can not reproduce with esearch-0.7.1-r6 and python 2.5.2

If this is still a problem, please reopen with esearch version and python version.