diff options
| author | andersen <andersen@69ca8d6d-28ef-0310-b511-8ec308f3f277> | 2004-06-22 10:18:30 +0000 |
|---|---|---|
| committer | andersen <andersen@69ca8d6d-28ef-0310-b511-8ec308f3f277> | 2004-06-22 10:18:30 +0000 |
| commit | a190629c14338250f04d55f3c1cf213c312b9241 (patch) | |
| tree | 94b214366ce9fe141a9c2489f84ca91f9bbfcafa /init | |
| parent | 854742837a9381bb24ee48f0cfeb628fa7eb27d5 (diff) | |
| download | busybox-w32-a190629c14338250f04d55f3c1cf213c312b9241.tar.gz busybox-w32-a190629c14338250f04d55f3c1cf213c312b9241.tar.bz2 busybox-w32-a190629c14338250f04d55f3c1cf213c312b9241.zip | |
Robin Farine writes:
Hi,
Package: BusyBox
Version: 1.0.0-pre10
When an incomplete read or write from/to a local file occurs (i.e.
not an EOF condition), the tftp client prematurely exits. This
problem can be reproduced by slowly piping data to the tftp client
like this:
(for v in 1 2 3; do echo $v; sleep 1; done) | \
tftp -p -l - -r output.txt <host>
The output file on the TFTP server will contain "1".
The attached patch provides a possible solution to this problem.
I can reproduce this on ARM sa1110 and ARM xscale boards, both
running Linux-2.6.4 & glibc-2.3.2. Thanks for the wonderful
program!
Robin
git-svn-id: svn://busybox.net/trunk/busybox@8915 69ca8d6d-28ef-0310-b511-8ec308f3f277
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions