Hi,
sorry, if my questions weren't precise enough
admin@??? <admin@???> (Mo 04 Dez 2017 07:21:39 CET):
> https://bugs.exim.org/show_bug.cgi?id=2206
>
> --- Comment #2 from Axel Reinhold <exim@???> ---
> > Did you compile it from the sources?
> yes - compiled from sources
Did you do a checkout from GIT or did you download the tarballs?
> > Are you able to do a bisect with the releases from 4.89 to 4.89.1? The
> > changelog shows two commits related to Berkley DB issues.
> >
> what do you mean with "do a bisect with the releases"?
If you're working with GIT, then you get the option to fast-find the
commit that introduced the bug.
Roughliy something like
git checkout exim-4_89_1
git bisect reset
git bisect start
git bisect bad
git bisect good exim-4_89
Now you got a commit between 4_89 and 4_89_1
Test it. After testing it, do a
git bisect <RESULT>
with <RESULT> being 'good' or 'bad'
and iterate until bisect found the commit that introduced the bug.
> > Do you see a way to reproduce the behaviour?
> >
> I can easyly reproduce the behaviour - these messages occur immediatelty after
> installing 4.89.1.
Can you post the output of
- exim -d -bV
- exim -bP config
On what system do you compile/use Exim? (OS, Distro, compiler used,
etcpp)
> > Can you share your configuration? Ideally the relevant parts only.
> How can i identify the "relevant parts" of the configuration? There are no use
> of berkeley-dbs in it which are obvious to me.
No 'dbm' and/or 'ratelimit' in your config? Then the only (implicit) use of DBM
are the retry databases.
Is it feasible to remove them (rm $spooldir/db/*)
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de ---------------------------- internet & unix support -
Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
gnupg encrypted messages are welcome --------------- key ID: F69376CE -
! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -
