On Sun, Sep 25, 2011 at 01:03:02PM +0200, Bernhard Schmidt wrote:
Since I do not have much knowledge about BDB, I'm at loss here. Do
you have any idea?
I had a nice talk with Stan a few weeks ago, and he advised that the
BDB database is actually little more than a cache. Current versions of
Hi Jörg,
I'm currently working on packaging a new version of Torrus into Debian.
I've tried the BDB Upgrade script Marc Haber wrote with your assistance,
but it does not work (at least not for the upgrade squeeze-wheezy (4.8
- 5.1).
The script Marc originally wrote included the flags
On Sun, Sep 25, 2011 at 01:03:02PM +0200, Bernhard Schmidt wrote:
Debian. I've tried the BDB Upgrade script Marc Haber wrote with your
assistance, but it does not work (at least not for the upgrade
squeeze-wheezy (4.8 - 5.1).
[...]
Since I do not have much knowledge about BDB, I'm at loss
On 25.09.2011 13:57, Joerg Dorchain wrote:
On Sun, Sep 25, 2011 at 01:03:02PM +0200, Bernhard Schmidt wrote:
Debian. I've tried the BDB Upgrade script Marc Haber wrote with your
assistance, but it does not work (at least not for the upgrade
squeeze-wheezy (4.8 - 5.1).
[...]
Since I do not
On Sat, May 24, 2008 at 07:31:45AM +0200, Joerg Dorchain wrote:
On Fri, May 23, 2008 at 04:41:31PM +0200, Marc Haber wrote:
On Fri, May 23, 2008 at 04:00:33PM +0200, Joerg Dorchain wrote:
I wrote a mini-version of db_recover in perl. Find it as an attachment.
Great. I would feel more
On Sat, May 24, 2008 at 10:25:16AM +0200, Marc Haber wrote:
[...]
Is this approach flawed?
Takes roughly twice the time.
But only if recover is really needed which is the rare exception.
What are we talking about, tens of seconds?
Yes, definitivly. Even a recover including a
On Thu, May 22, 2008 at 07:56:37PM +0200, Marc Haber wrote:
Upstream has rejected the patch since it will run recovery every time
a new process is started, breaking already running processes.
They instead suggest running db_recover unconditionally in the
postinst, which poses some challenge
On Fri, May 23, 2008 at 04:00:33PM +0200, Joerg Dorchain wrote:
I wrote a mini-version of db_recover in perl. Find it as an attachment.
Great. I would feel more comfortable though, if we'd only do the
recover if really necessary, such as in:
my $env = new BerkeleyDB::Env( -Home =
On Fri, May 23, 2008 at 04:41:31PM +0200, Marc Haber wrote:
On Fri, May 23, 2008 at 04:00:33PM +0200, Joerg Dorchain wrote:
I wrote a mini-version of db_recover in perl. Find it as an attachment.
Great. I would feel more comfortable though, if we'd only do the
recover if really necessary,
On Mon, May 05, 2008 at 12:07:18PM +0200, Joerg Dorchain wrote:
Maybe the attached one line patch could help. To my understanding of
torrus, perl, and berkeley-db it should fix the bug without side
effects.
I have forwarded this Upstream and will apply the patch if upstream
agrees. I don't
tags #476356 - patch - upstream
thanks
On Thu, May 22, 2008 at 04:12:54PM +0200, Marc Haber wrote:
On Mon, May 05, 2008 at 12:07:18PM +0200, Joerg Dorchain wrote:
Maybe the attached one line patch could help. To my understanding of
torrus, perl, and berkeley-db it should fix the bug without
tags #476356 patch,upstream
thanks
On Sun, May 04, 2008 at 10:33:18AM +0200, Marc Haber wrote:
Unfortunately, I do currently not have the time to write this
ten-liner as I don't know enough about berkeley db. I am therefore
tagging this bug help and would appreciate if somebody could write
tags #476356 help
thanks
On Wed, Apr 16, 2008 at 11:08:14AM +0200, Joerg Dorchain wrote:
while this sounds similiar to #408949, I think I found out the chain of
effects. torrus-common depends on libberkeleydb-perl, which in turn
depends on libdbX.X, what ever the current version is.
The
Package: torrus-common
Version: 1.0.6-2
Hello,
after an apt-get upgrade, torrus fails to start with messages in the
log:
[16-Apr-2008 08:30:44 ] Torrus version 1.0.6
[16-Apr-2008 08:30:44 ] /usr/share/torrus/bin/collector started for tree
main, instance #0
[16-Apr-2008 08:30:44*] Cannot create
14 matches
Mail list logo
