Mac wrote: > The data that's not being read/handled properly appears to be in > ~/.liferea_1.4/feedlist.opml and probably ~/.liferea_1.4/liferea.db > (though that doesn't open with a text editor - any ideas how to read the > contents?). I don't yet know what's causing the problem with the > handling of these...
It seems I was nearly right about the critical files, as indicated in the script here (a script for a situation more complex than mine, involving backing up with ssh): http://www.rolfs.no/2008/03/26/sync-lifereash-syncing-script/#more-99 where the essential files are indicated in these lines # Using rsync to preserve when file was last changed.. rsync -vaz -e "ssh" $REMOTE:$REMOTEDIR/feedlist.opml $BACKUPDIR/remote/ rsync -vaz -e "ssh" $REMOTE:$REMOTEDIR/liferea.db-journal $BACKUPDIR/remote/ rsync -vaz -e "ssh" $REMOTE:$REMOTEDIR/liferea.db $BACKUPDIR/remote/ rsync -vaz -e "ssh" $REMOTE:$REMOTEDIR/feedlist.opml.backup $BACKUPDIR/remote/ and much of the rest of the script seems to be about ensuring that these are the finalised and only files transferred and used (by making sure no copies of Liferea are running). The time stamps matter (of course - these are 'live' feeds); and that may be the problems with transferring the files via FAT32 - does the time stamp info disappear altogether, and cause a problem for the 'receiving' copy of Liferea? Completely out of my depth, now! Mac -- [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.org/UKTeam/
