[Gpe-list] gpesyncd

[Felix Joussein]

Hello Graham,

I have now tried to sync using this configuration to a h3800 unit which
also has the familiar 2.7 image installed.
Previously I was working on a h3900 unit, this was the device from which
I reported the problems.

I get now the same result - None.

ssh -l felix 192.168.41.2 gpesyncd --remote

does nothing...

Many thanks in advance, if you, or any other in that list could help me
to solve this issue.

Many thanks in advanced,

Felix


Graham Cobb wrote:
> On Wed, March 7, 2007 9:27, Felix Joussein said:
>   
>> <config>
>>   <use_local>0</use_local>
>>   <use_ssh>1</use_ssh>
>>   <handheld_ip>192.168.41.2</handheld_ip>
>>   <handheld_port>6446</handheld_port>
>>   <handheld_user>felix</handheld_user>
>> </config>
>>     
>
> If you have <use_ssh> set to 1, then you do not need to run gpesyncd
> yourself.  That setting tells the GPE plugin to connect to the handheld
> using SSH and run gpesyncd.  The GPE plugin will connect to the handheld
> using "ssh -l felix 192.168.41.2 gpesyncd --remote" (check it by hand to
> make sure it is working).  Any error running gpesyncd should appear on the
> terminal where you run msynctool (although it may be hard to see mixed up
> with all the other opensync output).
>
> If you set <use_ssh> (and <use_local>) to 0, then you DO need to run
> gpesyncd yourself with the --daemon qualifier.  You will also need to put
> the IP address of the desktop in ~/.gpe/gpesyncd.allow on the handheld. 
> In this case you should see gpesyncd listening on port 6446. But you do
> not need to do any of these things if you set <use_ssh> to 1.
>
> Graham
>
>
>
>   


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.