Re: GPILOTD Memofile Sync crash

[Lars Weissflog <L rs-w de>]

On Tue, 2003-07-22 at 00:44, Dagmar d'Surreal wrote:

> I don't even try to follow what rationale the debian guys use anymore. 
Well, regarding Evo they don't seem to do anything in the official
sense. All "Backports" I found are inofficial like the one I quoted.

> Try something simple and straightforward like:
> 
> ls -al /usr/share/gnome-pilot/conduits/e-*.conduit
> 

This gives

> ta carryme:~$ ls -al /usr/share/gnome-pilot/conduits/e-*.conduit
> -rw-r--r--    1 root     root          609 Jul 15 04:31 /usr/share/gnome-pilot/conduits/e-address.conduit
> -rw-r--r--    1 root     root          610 Jul 15 04:32 /usr/share/gnome-pilot/conduits/e-calendar.conduit
> -rw-r--r--    1 root     root          595 Jul 15 04:32 /usr/share/gnome-pilot/conduits/e-todo.conduit

So it looks they are in place. But they don't appear in the pilot-settings. Anyway, they are executed by gpilotd at hotsync. Strange.