Peer in conflict error, and kmlprint segfaults

Due to some messing around on my part starting and stopping
intersync, at various times, I managed to get two systems into a conflict.

So.. how do I tell the second system (which is set in 'data on demand'
mode on an ext3 filesystem, due to the patch I posted earlier), to
undo everything in it's KML?

The second problem 'kmlprint' and friends seem to always segfault.

Is there some documentation somewhere on what these programs are
supposed to do and how to deal with conflicts?

I'm running a 2.4.20 kernel on both machines, FYI.

-- 
--------------------------------------------------------------------------
Troy Benjegerdes                'da hozer'                [email protected]   

Somone asked my why I work on this free (http://www.fsf.org/philosophy/)
software stuff and not get a real job. Charles Shultz had the best answer:

"Why do musicians compose symphonies and poets write poems? They do it
because life wouldn't have any meaning for them if they didn't. That's why
I draw cartoons. It's my life." -- Charles Shultz


-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5