* Oswald Buddenhagen [2015-04-28 13:51]:
> On Tue, Apr 28, 2015 at 09:14:07AM -0400, Peter P. wrote:
> > head -5 .mbsyncstate.journal | hexdump -C
> >
> > 32 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > |2...|
> > 0010 00 00 00 00 00 00 00 00 00 00
Hello,
First thank you for this software. I appreciate your work.
I'm trying to get isync working on my qnap. The configure looks good (attached).
...
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 op
On Tue, Apr 28, 2015 at 03:45:15PM +0200, Tamas Papp wrote:
> I using Debian. I recently upgraded isync from 1.1.1-1 to 1.1.2-1. Since
> then I noticed that mbsync exits with a non-zero exit code even when
> there were no errors (checked with -DV).
>
> Is this intentional?
>
no.
first thing would
On Tue, Apr 28, 2015 at 09:14:07AM -0400, Peter P. wrote:
> head -5 .mbsyncstate.journal | hexdump -C
>
> 32 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |2...|
> 0010 00 00 00 00 00 00 00 00 00 00|..|
> 001a
>
uhm, ok, that doesn't look
Hi,
I using Debian. I recently upgraded isync from 1.1.1-1 to 1.1.2-1. Since
then I noticed that mbsync exits with a non-zero exit code even when
there were no errors (checked with -DV).
Is this intentional?
Best,
Tamas
--
* Oswald Buddenhagen [2015-04-28 07:36]:
> On Mon, Apr 27, 2015 at 10:07:40PM -0400, Peter P. wrote:
> > The contents of the .mbsyncstate.journal are
> > 2
> >
> ok, that's not helpful. :}
> please pipe the head command with hexdump -C and post that.
Thank you,
head -5 .mbsyncstate.journal |
On Mon, Apr 27, 2015 at 10:07:40PM -0400, Peter P. wrote:
> The contents of the .mbsyncstate.journal are
> 2
>
ok, that's not helpful. :}
please pipe the head command with hexdump -C and post that.
--
One dashboard
