First, thanks for such a speedy reply. This was not a show stopper. I just figured someone would look at in the distant future. I appreciate you taking the time to feedback.
> > We'd prefer to use inetutils-ping as it is included by > > default on most debian systems. And that makes it easily > > available to Docker images built on debian. > > (Just curious, but what do you mean with "included by default"? It's > Priority: extra, while iputils-ping is Priority: important.) I think this is my lack of knowledge about Debian's package system. What I mean to say was that I discovered that most of the Debian system's I'd logged into seemed to already have the 'inetutils-ping' version of ping installed. I had assumed this correlated to some sort of default installation since I had not specifically requested it in my builds. Once place where this really caught us was our use of Docker. All the Debian images (which sit at the base of tons of other images) all seem to include the 'inetutils-ping' version of ping, rather than the 'iputils-ping' editon. Obviously it's not a big deal to just define our own images and make a substitution -- but its extra maintenance and takes us away from the standard blessed images available from the Docker repos. I'll spend some time reading up on the priority attributes of debian packages to make sure any future communication is more precise. > > If you agree this is something that should be corrected, I > > believe it's a simple matter of adding fflush(STDOUT) around > > line 191 of ping_echo.c (just before the return from the > > function print_echo()). > > I think fixing this is fine, and I'll do so in my next upload. The > attached patch should do it. Perfect, Thanks again If you don't mind, I have one followup question regarding a comment you made: > Actually the problem is that stdout when redirected to a file switches > to fully buffered output, contrary to when writing to a terminal where > it does line buffering. Could you clarify this a bit more? Who is enabling file buffering? Is it the shell? Something in the plumbing of IPC/pipes? Something in the kernel? Any details would be greatly appreciated. Jim C. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
