On Wed, 2007-10-03 at 16:14 +0700, Patrick Shirkey wrote: > On Wed, 2007-10-03 at 00:02 -0400, Scott Gifford wrote: > > Patrick Shirkey <[EMAIL PROTECTED]> writes: > > > > > Hi Scott, > > > > > > Thanks for your in depth analysis. It seems that the culprit is: > > > > > > .synce/scripts/dccm.sh > > > > > > If I remove the dccm.sh script from the path I get the same result for > > > ppp0. Putting it back allows ppp0 to stay up. > > > > > > > That's interesting. It seems to imply that your device requires Raki > > to be running to stay up, but I don't know why that would be; I > > certainly didn't use Raki when I was syncing multiple PDAs. Maybe > > it's a configuration option somewhere? Maybe it would be useful to > > redirect output to a log file to see what's going on here? > >
I'm not a raki expert, but I can say with some confidence it does nothing to keep a connection alive. > > > > Maybe it would be useful to try shutting down Raki and see if anything > > different happens? Or maybe try compiling without > > "--enable-desktop-integration"? > > and see if that helps? > > --enable-desktop-integration is a slightly misleading name, it's the code that allows communication with odccm over dbus, it won't make any difference here. > > Maybe somebody with more recent knowledge of synce and Raki could step > > in here with an explanation of what might be going on? > > > > The other thing that's odd is that vdccm seems to be treating the two > > devices differently, and I don't know why that would be. The first > > device gets writeConnectionFile called, and also "dccm.sh connect", > > but the second device gets neither: > > The scripts won't help the situation, but they are a good indicator of whether the device is fully connected. > Hi Scott, > > I have been running the tests above without raki. > Excellent, I have no particular recommendations (sorry) but I think the raki discussion was starting to confuse the issue. Until you get it working I would use vdccm and the command line tools, nothing else is strictly necessary for a connectionand keeps it simple. Mark ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel