.

Block that file! |

It turns out that in order for the syncing to work you have to block the file.

In jpilot that’s pretty straight forward you just go to the Backup Menu and add the file.

For gpilotd - it’s a little more obscure. You have to edit .gnome2/gnome-pilot.d/backup-conduit

it has a field call exclude_files:

You provide a space seperated list of files and you are good to go. If you need to escape spaces use double slashes

I had to put two versions of the file name to get this to work - so my file has

exclude_files=WiFiCoreLib WiFiCoreLib.prc

But now it works!

Only one syncing problem left for me. I normally use Jpilot. But to do network syncing with it you have to run jpilot-sync so the port is open when you go to sync. Unfortunately on Ubuntu (Breezy) - jpilot-sync can’t load any of the plugins -which means no backups at all. Guess I’m headed to evolution full time till I can figure this out.

2 Responses to 'Block that file!'
  1. ed:

    If you set the port in j-pilot to “net:any” (instead of “/dev/ttyS0″) then you can sync over wifi without running jpilot-sync.

Leave a Reply

Moderation Active: Old stuff here... Therefore your comment on this post will be moderated (i.e. don't submit twice !)

    Categories
    Archives

    .