Syncing Remote File With Ko/pi

[rsay]

I am trying to sync korganizer calendar on my zaurus to an .ics file on my server. I have tried multiple permutations without success. Each time I am getting a message that the copy failed. The program suggests that I try the command on the command line to see what went wrong. The commands work fine on the command line so I don't know what to do next.

here are some of the settings that I have tried when configuring sync to remote file. I have SSH configured with shared keys to work without passwords. (I thought that would be the hardest step)

1st try:

download

Code: [Select]

scp -P 23 root@mydomain.org:/home/remotecalendar.ics /mnt/ide3/Documents/Pim_Files/localcalendar.ics
tmp

Code: [Select]

/mnt/ide3/Documents/Pim_Files/localcalendar.ics
upload

Code: [Select]

scp -P 23 /mnt/ide3/Documents/Pim_Files/localcalendar.ics root@mydomain.org:/home/remotecalendar.ics
2nd try:
download

Code: [Select]

scp -P 23 root@mydomain.org:/home/remotecalendar.ics /mnt/ide3/Documents/Pim_Files/localcalendar.ics
tmp

Code: [Select]

/tmp/mycalendar.ics
upload

Code: [Select]

scp -P 23 /mnt/ide3/Documents/Pim_Files/localcalendar.ics root@mydomain.org:/home/remotecalendar.ics
I won't list attempts 3,4,5,6,7,8, or 9

In both cases, the file gets downloaded to the proper place but then the program gives me the error message.

Does anybody have this working? Is there something else in the setup that I need to change? Am I downloading the file to the wrong place or giving it the wrong name? Am I using the wrong tmp file? Why does kdepimpi think that the copy failed, how does it determine if the copy was successful?

My setup:
Zaurus C3100 with pdaxrom rc12  running kdepimpi 2.2.3
Remote headless server running sshd to store the ics files
Multiple machines on the home network running the full kontact 3.4.3 suite that load the stored files from the server

[swing]

I am trying to sync korganizer calendar on my zaurus to an .ics file on my server.

When I was trying this (with the Windows version, but the principle is the same) I actually ran the commands from the command line to make sure each one was working - basically, the pre and post commands are run before and after syncing - so either the file is failing to copy, or the software simply doesn't like the downloaded file.

Try using a new file location on the server (one not used by all the other machines) and see if KO/Pi can sync the file to the server and back again.  Once you've got that working, then change over to the other file again.

[rsay]

I did some further experiments on this problem and things are looking more curious

If I manually copy my file into a directory from the command line

Code: [Select]

scp -P 23 -q root@mydomain.org:/home/fieldtrial.ics /mnt/ide3/Documents/Pim_Files/myfieldtrial.ics
Then, this command works in the sync configure script:

Down

Code: [Select]

cp /mnt/ide3/Documents/Pim_Files/myfieldtrial.ics /tmp/mycalendar.icsTemp

Code: [Select]

/tmp/mycalendar.icsUp    

Code: [Select]

cp /tmp/mycalendar.ics /mnt/ide3/Documents/Pim_Files/myfieldtrial.ics
However, this command set doesn't work:
Down

Code: [Select]

scp -P 23 -q root@mydomain.org:/home/fieldtrial.ics /tmp/mycalendar.icsTemp

Code: [Select]

/tmp/mycalendar.icsUp    

Code: [Select]

scp -P 23 -q /tmp/mycalendar.ics root@mydomain.org:/home/fieldtrial.ics
I have checked all individual commands from the command line. I have also verified that the permissions of the involved files are the same whether I do things manually or from within the program.

Any other thoughts?   Somebody please point out my stupid mistake!

[rsay]

I have now found another working combination that allows me to go forward, but I believe this is a bug.

If I create a script named fieldtrialdown.sh containing the following lines:

Code: [Select]

#!/bin/sh
scp -P 23 -q root@mydomain.org:/home/fieldtrial.ics /tmp/mycalendar.ics
I can then get things to work with the following commands

down

Code: [Select]

/mnt/ide3/usr/local/bin/fieldtrialdown.shtemp

Code: [Select]

/tmp/mycalendar.icsup    

Code: [Select]

scp -P 23 -q /tmp/mycalendar.ics root@mydomain.org:/home/fieldtrial.ics

Notice that the upload command works properly without requiring a script, but the download command does not. Does anybody know where I can report a bug to the kdepimpi team?

[swing]

Does anybody know where I can report a bug to the kdepimpi team?

This webpage gives Lutz's contact details, although he may respond here too.

Also, you can raise bugs via the sourceforge project here

[rsay]

When I went to sync the address book file I was able to use the same workaround as posted above for the calendar files, however, when I tried the same trick with the password files I ran into a different problem:

This command set fails

down

Code: [Select]

scp -P 23 -q root@mydomain.org:/home/mainpass.pwm /tmp/mypasswds.pwm
temp

Code: [Select]

/tmp/mypasswds.pwm
up

Code: [Select]

scp -P 23 -q /tmp/mypasswds.pwm root@mydomain.org:/home/mainpass.pwm
I then made up a script as follows and named it pwdown.sh:

Code: [Select]

#!/bin/sh
scp -P 23 -q root@mydomain.org:/home/mainpass.pwm /tmp/mypasswds.pwm
and the following command set also failed:

down

Code: [Select]

/mnt/ide3/usr/local/bin/pwdown.sh
temp

Code: [Select]

/tmp/mypasswds.pwm
up

Code: [Select]

scp -P 23 -q /tmp/mypasswds.pwm root@mydomain.org:/home/mainpass.pwm
I altered the script as follows:

Code: [Select]

#!/bin/sh
scp -P 23 -q root@mydomain.org:/home/mainpass.pwm /tmp/mypasswds.pwm
chmod 755 /tmp/mypasswds.pwm
Which allowed the passwords to sync properly. I am not sure why the password file would need to be executable in order to sync??

Hopefully someone else will find this useful or even better, maybe the developers will be able to use this information to make the program easier to use. I opened a bug at the sourceforge project page here:
http://sourceforge.net/tracker/index.php?f...103&atid=636951

I am quickly approaching my goal of having my calendars, addresses and passwords available to me at all of my computers

[zautrix]

Hopefully someone else will find this useful or even better, maybe the developers will be able to use this information to make the program easier to use.

I added the pi-sync mode to make it easier to use.

I never tried that complicated ssh fiddling with passwords - much too complicated for me.

z.