On Thursday 04 October 2007, Patrick Shirkey wrote: > On Wed, 2007-10-03 at 15:16 +0200, Volker Christian wrote: > > On Wednesday 03 October 2007, Patrick Shirkey wrote: > > ... > > > > > > > ++++++++++++++++++++++++++++++++++++++ > > > > > more .synce/scripts/dccm.sh > > > > > #!/bin/sh > > > > > > > > > > case "$1" in > > > > > > > > > > connect) > > > > > ;; > > > > > > > > > > disconnect) > > > > > ;; > > > > > > > > > > start|stop) > > > > > raki=`dcop | grep raki` > > > > > dcop $raki Raki "dccmNotification(QString)" $1 > > > > > 2> /dev/null > /dev/null > > > > > ;; > > > > > > > > > > install) > > > > > ;; > > > > > > > > > > uninstall) > > > > > ;; > > > > > > > > > > *) > > > > > echo "Help!" > > > > > ;; > > > > > esac > > > > > ++++++++++++++++++++++++++++++++++++++ > > > > > > Hi Scott, > > > > > > I have been running the tests above without raki. > > > > > > Disabling the desktop integration on libsynce and vdccm did not change > > > anything. > > > > > > It would be helpful if someone could explain what the dccm.sh script is > > > for. > > > > > > > > > Cheers. > > > > Hi, > > > > a unix-socket (~.synce/csock) is used for the normal communication > > between vdccm and raki. vdccm is the server, and raki connects to it. > > Thus, there is no need for a script for normal operation. > > Nevertheless, if raki is started before vdccm, it has to be notified when > > vdccm has created the server-socket (~.synce/csock). For this the above > > script is used, which is executed by vdccm during startup, to force raki > > to connect to vdccm. > > If you start raki after vdccm, this script is useless. > > So is it a bug that my first device only connects for about three > seconds if I remove the dccm.sh script even though I don't have raki > running and it works very well if I leave dccm.sh in place? For that to know, it is necessary for me to know the device-type you use. Is is t pre-WM5 device of a WM5 device?
Pre-WM5 devices connect by themself to vdccm and start talking to it. WM5 devices need the triggerconnection-command for initiating a connection to vdccm. It will be a very strange behavious if your device initially starts talking to vdccm and disconnect a view seconds. Maybe there is a firewall running somehow which prevents vdccm sending the "ping" packages to the device and/or prevents receiving the "pong" packages back. Try to start vdccm with "-d 5 -s 2" and have a look at the output of vdccm - every 2 seconds a ping-package should be send to the device and the corresponding "pong" package should be received. If this isn't the case you have some fundamental connection problems to you device. regards voc > > - I have removed the scripts from /etc/udev/rules/ > > But that doesn't make any difference. > > > Cheers. ------------------------------------------------------------------------- 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