On Wed, Apr 29, 2015 at 02:39:42PM +0200, Oswald Buddenhagen
wrote:
> On Wed, Apr 29, 2015 at 01:00:07PM +0100, Charlie Allom wrote:
> > I was just wondering if there was a way to read the debug output to
> > fix "Notice: conflicting changes in (422568,85716)" alerts without
> > resetting the who
On Wed, Apr 29, 2015 at 02:39:11PM +0200, Tamas Papp wrote:
> Thanks for the suggestion. I did run
>
> valgrind --tool=memcheck --log-file=/tmp/mbsync /usr/bin/mbsync -a
>
> and got quite a few 'Use of uninitialised value of size 8' and even more
> 'Conditional jump or move depends on uninitialis
hi Oswald,
Thanks for the suggestion. I did run
valgrind --tool=memcheck --log-file=/tmp/mbsync /usr/bin/mbsync -a
and got quite a few 'Use of uninitialised value of size 8' and even more
'Conditional jump or move depends on uninitialised value(s)' messages.
1. is this the right command line, o
On Wed, Apr 29, 2015 at 01:00:07PM +0100, Charlie Allom wrote:
> I was just wondering if there was a way to read the debug output to
> fix "Notice: conflicting changes in (422568,85716)" alerts without
> resetting the whole thing?
>
you mean, you get the exact same message over multiple runs despi
Hello,
I was just wondering if there was a way to read the debug output to fix
"Notice: conflicting changes in (422568,85716)" alerts without resetting the
whole thing?
C.
--
0x8486EDA8
http://spodder.com/
--
One
On Tue, Apr 28, 2015 at 03:43:40AM -0500, doc1623 wrote:
> checking for Berkley DB >= 4.2... yes
> ...
>
> [admin@QNAPNAS isync-1.1.3]# isync
> isync: error while loading shared libraries: libdb-4.2.so: cannot open
> shared object file: No such file or directory
>
>
> The configure seems to find
