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. regards voc ------------------------------------------------------------------------- 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
