[spambayes-bugs] [ spambayes-Feature Requests-1383810 ] Don't buffer STDOUT and STDERR
SourceForge.net
noreply at sourceforge.net
Sun Apr 2 14:37:39 CEST 2006
Feature Requests item #1383810, was opened at 2005-12-18 08:11
Message generated for change (Comment added) made by anadelonbrin
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=498106&aid=1383810&group_id=61702
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: pop3proxy
Group: None
>Status: Closed
Priority: 5
Submitted By: lyeoh (lyeoh)
Assigned to: Nobody/Anonymous (nobody)
Summary: Don't buffer STDOUT and STDERR
Initial Comment:
It is desirable to allow sb_server STDOUT/STDERR to be
unbuffered so that sb_server STDOUT and STDERR appears
in syslog in a timely manner
e.g.
sb_server.py | logger -t spambayes 2>&1 &
I am currently adding -u
e.g.
#!/usr/local/bin/python -u
Otherwise nothing shows up in syslog until the buffer
is flushed which is not on a per line basis.
----------------------------------------------------------------------
>Comment By: Tony Meyer (anadelonbrin)
Date: 2006-04-03 00:37
Message:
Logged In: YES
user_id=552329
If you are running from source, then it is up to you what
you pass to Python as stdout/stderr/stdin. If this is what
you want, then you could achieve the same effect with
python -u sb_server.py | logger -t spambayes 2> &1 &
without having to modify any of the files.
For the binary versions, we open the log files unbuffered.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=498106&aid=1383810&group_id=61702
More information about the Spambayes-bugs
mailing list