On Tue, Apr 28, 2015 at 09:14:07AM -0400, Peter P. wrote: > head -5 .mbsyncstate.journal | hexdump -C > > 00000000 32 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |2...............| > 00000010 00 00 00 00 00 00 00 00 00 00 |..........| > 0000001a > uhm, ok, that doesn't look too well. i can only speculate how it came to be. there is nothing to lose by deleting this file. you may want to compare .mbsyncstate.new with .mbsyncstate first, though. if the .new file is different and looks sane, it should be probably renamed over the old one.
------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
