Udpcast May 2011

udpcast@udpcast.linux.lu

1 participants
8 discussions

by George Coulouris

Hello, 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 int ret; ... if(pipePid) { ret=udpc_waitForProcess(pipePid, "Pipe"); } ... return ret; <---- cut here Regards, George Coulouris National Center for Biotechnology Information (contractor)

11 years, 1 month

patch submit: Use "flprintf()" on every printout on stderr

by Julien Aube

Hello, While using udpcast, I found out that it may be very verbose on stderr, even if a logfile is specified. This turns out to be a problem for our embedded application where the stderr is a (slow) serial port. So here is a patch which replace every occurrence of fprint(sdterr,...) by the flprintf() function defined in log.c. I thought it might be of some use for people. (This patch also happen to cleanup the blank spaces at end of lines) Julien -- People in the embedded space don't do prototypes. They hack something until it works, then it's done. --- Always code as if the person who will maintain your code is a maniac serial killer that knows where you live

11 years, 10 months

castomize udpcast iso image

by Gianluigi Autuori

I want to use Udpcast from iso image in this scenario: - first pc boots from udpcast iso image -second pc boots from ethernet using pxe that sends him udpreceiver How can I do it? thanks

11 years, 10 months

patch submit: Provide a watchdog on receiver

by Julien Aube

Hello, I've made the attached patch to prevent the situation where the udp-receiver hang out indefinitly waiting for data when the server has been killed after having started to send data. In this case, the udp-received program would hang indefinitly. Since in my program, udp-receiver is called through system(...); the result is a hang. With this patch I use a SIGALARM signal to reset a flag to 0, and act as a watchdog. The watchdog is started just before the sending data phase of the protocol, and is feed each time a packet is received from the server. If 2 times in a row the watchdog is not feed, the program exit in error. The current value is set as a #define as 60s, which is in effect 2mn before udp-receiver is actually killed. However I am aware that this implementation is somehow crude, and I would be interested by any other way to do that. Additionally, if someone is interested by this patch, I could make it so that the watchdog period is configurable on the command-line. Thanks for your time, Julien -- People in the embedded space don't do prototypes. They hack something until it works, then it's done. --- Always code as if the person who will maintain your code is a maniac serial killer that knows where you live

11 years, 10 months

Support for Apple iMac keyboards (hid_apple) in udpcast images

by Frederik Himpe

I tried booting a recent Apple iMac with the latest kernel and an initrd from cast-o-matic, but the kayboard fails to work. Looking at an installed Debian system, the module hid_apple is loaded. Is this driver missing from the udpcast images, and is it possible to add it? -- Frederik Himpe <fhimpe(a)vub.ac.be> Vrije Universiteit Brussel

11 years, 10 months

Socket problem in receiver

by Sergio Sánchez Vega

Hello, I´m using latest udpcast versión (20100130) in Debian machines to transfer files in unidirectional mode. Sometimes I see the next message in receiver machine: Receiver error After putting some fprintf I realized the problem is in the file udpr-negotiate.c in line 191: sock = udpc_selectSock(client_config.socks, NR_CLIENT_SOCKS, net_config->startTimeout); if(sock < 0) { return -1; } Why sock is < 0? What should I do? Thanks

11 years, 11 months

static compile

by cruejones＠comcast.net

Is there an easy way to statically compile udpcast? currently: # ldd udp-receiver linux-vdso.so.1 => (0x00007fffde082000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fd71bef7000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fd71bcda000) libc.so.6 => /lib64/libc.so.6 (0x00007fd71b97c000) /lib64/ld-linux-x86-64.so.2 (0x00007fd71c0fb000) thanks

11 years, 11 months

Feature request: MBR-only cloning

by gencap＠email.it

It would be useful to have in device selection menu, in addition to whole hard drive and partitions (hda, hda1..hdn), a "MBR-only" item (e.g. to access just the first 512 bytes of the device). Cloning a single partition it's usually enough (and it's the typical use) but when the source partition has been resized, transferring the whole drive could be a waste of time. Of course, I'm referring to cast-o-matic generated images: with a full-blown environment it's easy to "dd" and cast the MBR. Another task that is pretty common in a classroom or lab environment, is cloning the CMOS memory: I'm using a DOS based utility but with a bunch of lines of code it should be possible to patch busybox to handle CMOS memory operations. -- Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it: http://www.email.it/f Sponsor: Prenota la Vacanza entro il 20/5 un bambino fino 12 anni in camera con i genitori GRATIS (min 7 notti)Pens Compl da Euro 60. Sardegna-Castelsardo Hotel Pedraladda Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=11439&d=20110517

11 years, 11 months

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Udpcast May 2011