If udp-receiver is writing to a pipe and the pipe fails, udp-receiver
will incorrectly exit with a returncode of zero. This is easily tested
with a trivial pipe program that copies stdin to stdout, but exits with
a nonzero status upon encountering eof.
Adding the following to startReceiver() in udpr-negotiate.c is
sufficient to fix this behavior:
<---- cut here
<---- cut here
National Center for Biotechnology Information (contractor)
I am using Udp-cast and I am happy, but some of the new mashines I have
bourght dont work with it. The kernel dont know my harddisk-controler (I
think) så it cant find my disks.
Are you planning to make a new version soon, with kernel 3?
Gunner Poulsen Teacher Denmark.
I have 2 big problem with wonderful program udpcast on Solaris 10 ( with Linux all works fine but it's not my case ):
First is udp-sender:
# udp-sender --interface e1000g1 --async --max-bitrate 10m --fec 8x8 --pointopoint --mcast-data-address 192.168.0.2 --file /tmp/Beyonce-Run.tar
stripes=8 redund=8 stripesize=128
UDP sender for /tmp/Beyonce-Run.tar at 192.168.0.1 on e1000g1
Broadcasting control to 192.168.0.255
Ready. Press any key to start sending data.
Starting transfer: 00000029
bytes= 85 698 704 re-xmits=0000000 ( 0.0%) slice=1024 - 0
udp-sender hang at this point after file transfer. I never get message "File transfer". I can stop process with CTRL-C
But udp-receiver get file completely and exit with appropriate message.
Second is udp-receiver and "--receive-timeout" option. It doesn't work in Solaris 10.
Can these problems be fixed?