On Wed, 2011-01-19 at 21:10 +0100, Karl Relton wrote: > Mark > > So sorry for length of time to replying - for some reason your reply on > 24/12 didn't seem to hit my inbox. > > > By 'connecting multiple times', do you mean unplugging and re-plugging > my WM2003 device? >
Yep. > If I do that, then indeed I am getting a dccm related issue. From my > syslog: > > Jan 19 19:58:48 dellpc hal-dccm[4419]: DEBUG: create_device: found > device interface > Jan 19 19:58:48 dellpc hal-dccm[4419]: CRITICAL: create_device: unable > to listen on rndis port (990), server invalid > > > I have to kill hal-dccm and re-plug again, and then it works. > > Ahh nuts. This is the one thing keeping me from releasing this..... I actually have no idea how to fix it at the moment, but I know exactly why it happens. When a device connects, we open a listening tcp server on port 990 and 5679, the first is for WM5 and the second is for 'legacy'. We do both because we dont know what kind it is yet. When the Wm2003 device connects to port 5679, we close the server on 990 because we don't need it. But it doesn't close on 990, so when the device is unplugged and replugged, we again open both servers, but 990 failed to close, so when we try and open it we get an error. I've gone right down to trying to close the file descriptor manually, no good. It's bound to be something obvious. Anyone that spots it gets to be King of Synce !!!!!! > I think my new udev rules and thus simplified udev-synce-serial (as per > my patch) are good. Happy to try and debug hal-dccm if you can give me > some pointers. > > Karl > > > > > Hi Karl > > > > Apologies, I should have replied earlier. > > > > The ubuntu package is actually a bit out of date, so I've already added > > some of the fixes you've been sending. I'll upload a new one as soon as > > I can. > > > > I'll also take a look at the below. I would rather do this at the udev > > level, but I couldn't figure out how. If you've cracked it that will be > > great. > > > > The main problem that had stopped me releasing the udev stuff was with > > pre WM 5 devices. It worked connecting once, but to connect again I had > > to kill dccm. I've now managed to lose my WM2003 test device, can you > > try connecting multiple times and confirm if it works or not ? > > > > Thanks > > Mark > > > > > I've done some digging, and worked out that the device querying code in > > > udev-synce-serial is only necessary for trying to handle two-port > > > devices. I think this can be better handled in the udev rules, from > > > which we can launch udev-synce-serial only when required (i.e. on the > > > 2nd port of a two port device), and thus remove all that logic from > > > udev-synce-serial itself. > > > > > > That means udev-synce-serial no longer has to call udevadm or use a > > > library to interrogate the udev database, cutting a chunk of code. > > > > > > The patch below does just that. > > > > > > Regards > > > Karl > > > ------------------------------------------------------------------------------ > Protect Your Site and Customers from Malware Attacks > Learn about various malware tactics and how to avoid them. Understand > malware threats, the impact they can have on your business, and how you > can protect your company and customers by using code signing. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > SynCE-Devel mailing list > SynCE-Devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/synce-devel
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
