From julien.aube at openwide.fr Mon Sep 13 11:59:11 2010 From: julien.aube at openwide.fr (Julien Aube) Date: Mon, 13 Sep 2010 11:59:11 +0200 Subject: [Udpcast] patch submit: Provide a watchdog on receiver Message-ID: <4C8DF5EF.30207@openwide.fr> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: udpcast_add_receiver_watchdog.patch Type: text/x-diff Size: 2466 bytes Desc: not available URL: From julien.aube at openwide.fr Mon Sep 13 11:50:51 2010 From: julien.aube at openwide.fr (Julien Aube) Date: Mon, 13 Sep 2010 11:50:51 +0200 Subject: [Udpcast] patch submit: Use "flprintf()" on every printout on stderr Message-ID: <4C8DF3FB.70104@openwide.fr> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: udpcast_cleanup_whitespace_and_force_flprintf.patch Type: text/x-diff Size: 55798 bytes Desc: not available URL: From fhimpe at vub.ac.be Thu Sep 23 16:30:21 2010 From: fhimpe at vub.ac.be (Frederik Himpe) Date: Thu, 23 Sep 2010 16:30:21 +0200 Subject: [Udpcast] Support for Apple iMac keyboards (hid_apple) in udpcast images Message-ID: <1285252221.1160.2.camel@defected.localdomain> 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 Vrije Universiteit Brussel From ssanchez at s30labs.com Thu Sep 30 14:14:00 2010 From: ssanchez at s30labs.com (=?iso-8859-1?Q?Sergio_S=E1nchez_Vega?=) Date: Thu, 30 Sep 2010 14:14:00 +0200 Subject: [Udpcast] Socket problem in receiver Message-ID: <000601cb6098$f7b3c3c0$e71b4b40$@com> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: