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 was just looking out for drivers for NIC and Hard Disk. Their model
numbers are as follows,
1) Realtek RTL8168C(P)/8111C(P) Family PCI-E Gigabit Ethernet NIC(NDIS
1) WDC WD2500 AAJS-60M0a0 ATA DEVICE
2) Hitachi HDP725016GLA380 ATA DEVICE
Can you suggest me any other driver which can be compatible with this model
of the hardware.
--nosync do the trick
But still a lot of re-xmits, ie
root@debian:~# udp-sender --file /dev/sda6 --interface eth0 -P 9000
bytes= 24 038 355K re-xmits=2071665 ( 12.2%) slice=0112 - 0
Timeout notAnswered= notReady= nrAns=0 nrRead=0 nrPart=1 avg=743
Timeout notAnswered= notReady= nrAns=0 nrRead=0 nrPart=1 avg=923
bytes= 24 143 004K re-xmits=2080485 ( 12.2%) slice=0112 - 0
Disconnecting #0 (192.168.10.21)
root@debian:~# udp-receiver --file /dev/sda6 --nosync --interface eth0 -P
UDP receiver for /dev/sda6 at 192.168.10.21 on eth0
received message, cap=00000009
Connected as #0 to 192.168.10.16
Listening to multicast on 184.108.40.206
Press any key to start receiving data!
bytes= 24 143 004K (439.79 Mbps))
2012/1/19 Raul Sanchez <raul(a)um.es>
> Have you try to use "--no-sync" option?
> I had a similar problem and i solved it that way. I think that udpcast has
> change its default settings in any cases.
> Lluís Gras <lluisgg(a)joseptous.info> escribió:
> Sorry for my English.
> I have been using udpcast (PXE or a custom Debian Live) over the past two
> years (version 20100130) and I recently upgraded to the latest version (
> 20110710), the old version got a transfer rate of about 480Mbps, withfeww
> reemissions (approximately 10 re-xmits) with the new and the same teams
> involved does not exceed 43 Mbps. I tried to disable ipv6 (ipv6.disable =
> 1) but there was no difference.
> If I use the udp-sender (20110710) with the udp-receiver (20100130)
> recovered the rate of 480 Mbps.
> How do I find out why the number of re-xmits increases significantly?
> Thanks in advance
Sorry for my English.
I have been using udpcast (PXE or a custom Debian Live) over the past two
years (version 20100130) and I recently upgraded to the latest version (
20110710), the old version got a transfer rate of about 480Mbps, with feww
reemissions (approximately 10 re-xmits) with the new and the same teams
involved does not exceed 43 Mbps. I tried to disable ipv6
(ipv6.disable = 1) but
there was no difference.
If I use the udp-sender (20110710) with the udp-receiver (20100130)
recovered the rate of 480 Mbps.
How do I find out why the number of re-xmits increases significantly?
Thanks in advance
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.