Anonymous | Login | Signup for a new account | 11-10-2008 10:43 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0000180 | [BusyBox] Networking Support | minor | always | 03-22-05 11:36 | 12-15-05 00:20 | ||||
Reporter | tldinnc | View Status | public | ||||||
Assigned To | BusyBox | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | 1.00 | ||||||
Summary | 0000180: ping output is buffered | ||||||||
Description |
ping's packet-by-packet output is buffered (more than a single line) when not going to a terminal. If the output is piped, lines are not received one-by-one as expected. This is minor unless you want to manipulate the output programmatically in "real time". |
||||||||
Additional Information |
The addition of a single strategically placed fflush(stdout) repairs the issue (circa line 332 in ping.c). I have no need for ping6 so I didn't test it, but it may suffer from a similar problem. The idea for the repair was suggested by looking at Debian iputils-ping source. |
||||||||
Attached Files | |||||||||
|
Copyright © 2000 - 2006 Mantis Group |