Just so you know, the policies of most Linux distributions forbid this
kind of bundling, so unless it's easily disabled (and preferably
defaults to using system libraries) the distributions will just have to
patch it back out again. For example, here's the Fedora policy:
http://fedoraproject.org
r own crc32 and sha1 implementations in
> the code.
>
>> BTW, a basic question: why do we face more problems with Berkeley DB
>> than
>> with other file formats?
>
> Environments mainly. It does this funky "environment" thing which makes
> it very susce
deeply integrated into the rest of the system.
The other interesting one is openssl - but I don't think we have many
problems with it. Not having openssl kind of sucks with 2.4 though.
Would suck less if we put our own crc32 and sha1 implementations in
the code.
> BTW, a basic question:
ut the sysadmin who just wants a stable Cyrus
server probably cares less about taste than stability.
BTW, a basic question: why do we face more problems with Berkeley DB than
with other file formats?
Shuvam
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Hello Toomas
2008/2/7, Toomas Aas <[EMAIL PROTECTED]>:
> > I use FreeBSD 6.3 with cyrus imapd 2.3.11. How I can check the
> > Berkeley DB version? I read a lot over the db_... tools but I have no
> > idea which files I should check for what. They reside in /var/imap
Martin Schweizer wrote:
> I use FreeBSD 6.3 with cyrus imapd 2.3.11. How I can check the
> Berkeley DB version? I read a lot over the db_... tools but I have no
> idea which files I should check for what. They reside in /var/imap?
pkg_info | grep db should show you which Berkeley DB pa
Hello
I use FreeBSD 6.3 with cyrus imapd 2.3.11. How I can check the
Berkeley DB version? I read a lot over the db_... tools but I have no
idea which files I should check for what. They reside in /var/imap?
Regards,
--
Martin Schweizer
[EMAIL PROTECTED]
Tel.: +41 32 512 48 54 (VoIP)
Fax: +1
> -Original Message-
> From: Alex Prinsier [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 09, 2007 11:06 AM
> To: Leon Kolchinsky
> Cc: info-cyrus@lists.andrew.cmu.edu
> Subject: Re: unable to open Berkeley db /etc/sasldb2: Permission denied
>
> Try:
&
-
> Jan 9 10:28:20 mail pop3[25728]: unable to open Berkeley db /etc/sasldb2:
> Permission denied
> Jan 9 10:28:23 mail pop3[25728]: unable to open Berkeley db /etc/sasldb2:
> Permission denied
> Jan 9 10:29:55 mail pop3[25728]: unable to open Berkeley db /etc/sa
Hello All,
I have a working mail system Cyrus+Postfix+Web-cyradm+Amavisd-new(SA+ClamAV)
with 2 virtual domains.
All is working, but I've noticed that I keep getting:
--
Jan 9 10:28:20 mail pop3[25728]: unable to open Berkeley db /etc/sa
Hi,
When compiling the latest cyrus imap server 2.2.12 with berkeley db
4.5.20 on Solaris 9 with gcc I get this error:
==CUT==
[EMAIL PROTECTED]:/tmp/cyrus-imapd-2.2.12> gmake
### Making all in /tmp/cyrus-imapd-2.2.12/man
gmake[1]: Entering directory `/tmp/cyrus-imapd-2.2.12/man'
n, but is apparently outdated a bit.
In another posting to this list, Andrew Morgan hinted that "Cyrus
v2.2.12 and older will not work with Berkeley DB 4.3+ without a patch".
With 2.2.13, at least I get a meaningful error out of Berkeley when I
start Cyrus:
DBERROR db4: Skipping log fi
Cause for concern, or par for the course? :)
My situation is that I'm working on getting lmtpproxy frontends to work,
and they do. But every time a message is delivered, the lmtp process on
the frontend machine also logs these additional lines:
Aug 30 09:21:02 frontend lmtp[5079]: DBERROR d
arted building cyrus-imapd-2.2.13 - the Cyrus homepage still lists
2.2.12 as the 'current' version, but is apparently outdated a bit. In another
posting to this list, Andrew Morgan hinted that "Cyrus v2.2.12 and older will
not work with Berkeley DB 4.3+ without a patch". With
om the system, so it shouldn't even be using
Berkeley-db anymore, with all databases being skiplist.
Starting with a clean /var/imap, I can start the newly compiled Cyrus,
so it has to do with whatever is left in /var/imap/db from the old
Berkeley version.
I've also done a db_upgrade
On Mon, 28 Aug 2006, Paul Boven wrote:
Hi everyone,
A bit over a month ago I tried to upgrade the Berkeley DB on a Cyrus-2.2.12
mailserver. That didn't work out because right at startup, 'ctl_cyrusdb -r'
would fail with 'critical dabase situation'.
After a bit
Hi everyone,
A bit over a month ago I tried to upgrade the Berkeley DB on a
Cyrus-2.2.12 mailserver. That didn't work out because right at startup,
'ctl_cyrusdb -r' would fail with 'critical dabase situation'.
After a bit of debugging, I've gotten things d
figure out what is what:
# file mailboxes.db
mailboxes.db: Apple QuickTime movie file (skip)
That is a skiplist file...
# file /etc/mail/aliases.db
/etc/mail/aliases.db: Berkeley DB (Hash, version 7, native byte-order)
That is a bdb file.
On your production system you should be able to use:
#
m Berkeley on each of
these databases? And which databases exactly would that be? This is a
stock standard 2.2.8, with no specific backends mentioned in the
imapd.conf or compiled in. What are the filenames/locations where I
should find Berkeley db files?
If it where me I would downgrade your b
;m wondering: should I call db_upgrade from Berkeley on each of
>> these databases? And which databases exactly would that be? This is a
>> stock standard 2.2.8, with no specific backends mentioned in the
>> imapd.conf or compiled in. What are the filenames/locations where I
>>
pgrade from Berkeley on each of
> these databases? And which databases exactly would that be? This is a
> stock standard 2.2.8, with no specific backends mentioned in the
> imapd.conf or compiled in. What are the filenames/locations where I
> should find Berkeley db files?
>
>
And which databases exactly would that be? This is a
stock standard 2.2.8, with no specific backends mentioned in the
imapd.conf or compiled in. What are the filenames/locations where I
should find Berkeley db files?
Some candidates:
/var/imap/mailboxes.db - but Berkeley-db fails to recognise
https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2187
This bugzilla entry is similar to what I've reported:
configure finds the header of some 3.x version of Berkeley DB, but
linking is tried with db-4.0.
Can this be fixed in a way that will allow linking with db3.x ?
Thank you,
Adrian Buc
> bdb-libdir will determine -L linker option, while bdb-incdir will
> determine -I (uppercase i) option and indirectly, via version in the
> header, -l (lowercase L) option, the version known internally by cyrus
> and optionally rpath.
>
> Regards,
> Adrian Buciuman
>
Sorry, I've made a mistake.
particular version of berkeley db.
Neither should it require patches in order to compile in common
scenarios. My impression is that some packages are patching cyrus to
select the right bdb. If true, this is bad. Selection of bdb version
should be done by configure options, not by configure-like pat
Adrian Buciuman wrote:
On 12/12/05, Ken Murchison <[EMAIL PROTECTED]> wrote:
I am pleased to announce the release of Cyrus IMAPd 2.3.0. This is an
BETA-quality release
I'm trying to compile it on Slackware.
How can I elegantly select which Berkeley DB to use?
I want to us
On 12/12/05, Ken Murchison <[EMAIL PROTECTED]> wrote:
> I am pleased to announce the release of Cyrus IMAPd 2.3.0. This is an
> BETA-quality release
I'm trying to compile it on Slackware.
How can I elegantly select which Berkeley DB to use?
I want to use libdb-3.3, which is t
:33 spock lmtpunix[17298]: DBERROR db4: Berkeley DB library
configured to support only DB_PRIVATE environments
Nov 24 17:12:33 spock lmtpunix[17298]: DBERROR: dbenv->open '/var/lib/imap/db'
failed: Invalid argument
Nov 24 17:12:33 spock lmtpunix[17298]: DBERROR: init() on berkeley
No
meone releasing a
> new version that breaks your patch anymore.
>
> It's great running old software, and making it work the way it should
> be(tm) to begin with.
I just wanted to say that the largest of our production servers run
Berkeley DB 3.3.11: (July 12, 2001). And I don
lpha (No, it is not HP, nor
> Compaq, I do not recognize those assholes as the bearers of the brand
> Alpha and Tru64) - on Berkeley DB 4.2.52 + patches. They run smoothly.
>
> Would I gain anything by upgrading (and recompiling all my packages)
> to BDB 4.3 or 4.4?
>
> Providing,
is not HP, nor Compaq, I do
not recognize those assholes as the bearers of the brand Alpha and
Tru64) - on Berkeley DB 4.2.52 + patches. They run smoothly.
Would I gain anything by upgrading (and recompiling all my packages) to
BDB 4.3 or 4.4?
Providing, of course, Ken can fix Cyrus so
-- Henrique de Moraes Holschuh said the following on 11/18/05 5:14 PM:
On Fri, 18 Nov 2005, Ken Murchison wrote:
[EMAIL PROTECTED] wrote:
http://www.sleepycat.com/products/bdb.html
Great! I'm still applying 4.3 compat fixes.
My thoughts exactly. And I am also wondering how many extremely w
On Fri, 18 Nov 2005, Ken Murchison wrote:
> [EMAIL PROTECTED] wrote:
> >http://www.sleepycat.com/products/bdb.html
>
> Great! I'm still applying 4.3 compat fixes.
My thoughts exactly. And I am also wondering how many extremely weird
bugs we will get this time around... 4.2 was a complete and ut
[EMAIL PROTECTED] wrote:
http://www.sleepycat.com/products/bdb.html
Great! I'm still applying 4.3 compat fixes.
--
Kenneth Murchison
Systems Programmer
Carnegie Mellon University
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/I
http://www.sleepycat.com/products/bdb.html
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
tm is in sys/time.h or
time.h... time.h
checking for struct tm.tm_zone... yes
checking for vprintf... yes
checking for _doprnt... no
checking authorization method... unix
checking db.h usability... yes
checking db.h presence... yes
checking for db.h... yes
configure: error: Berkeley
DB 3.x
to upgrade it ? or
is it not very important, in which case I can delete it and start from
scratch.
Thank you very much
Pascal
Sandra wrote:
I was trying the same procedure here : upgrade problem 2.0.16
Berkeley DB 3 to 2.2.12 Berkeley DB 4
I have used the ctl_mboxlist -d to dump t
> I was trying the same procedure here : upgrade problem 2.0.16 Berkeley
> DB 3 to 2.2.12 Berkeley DB 4
>
> I have used the ctl_mboxlist -d to dump the old db3 mailboxes.db file ,
> on the old machine . After a copy to the new
> machine with 2.2.12 Berkeley DB 4, I did a ctl_m
I was trying the same procedure here : upgrade problem 2.0.16 Berkeley
DB 3 to 2.2.12 Berkeley DB 4
I have used the ctl_mboxlist -d to dump the old db3 mailboxes.db file ,
on the old machine . After a copy to the new
machine with 2.2.12 Berkeley DB 4, I did a ctl_mboxlist -u., and a new
Pascal Mouret wrote:
Has anybody got an idea ? Where did I go wrong ? Could it be a result of
running version 2.2.12 cvt_cyrusdb while 2.0.16 is still up ?
Running two different versions (or even having them present on the
system) of BDB libraries is always somewhat a problem. Save yourself
a l
Hello all,
I am having quite some troubles upgrading from cyrus imap 2.0.16 to 2.2.12.
The problem (of these past fews days) comes from the mailboxes.db which
I fail to convert to skiplist.
The current cyrus imapd 2.0.16 was compiled using berkeley db 3, while I
compiled the new 2.2.12 with
Hello All,
After installing cyrus imap I get this error in the imapd.log
Jun 6 14:26:20 lb01-s06 cyr_expire[25505]: incorrect version of
Berkeley db: compiled against 4.3.28, linked against 4.1.25
Jun 6 14:26:20 lb01-s06 master[25506]: about to exec /usr/cyrus/bin/ctl_cyrusdb
Jun 6 14:26:20
s : SunOS
> os-version : 5.9
> environment: Built w/Cyrus SASL 2.1.20
> Running w/Cyrus SASL 2.1.20
> Built w/Sleepycat Software: Berkeley DB 4.3.27: (December 22,
> 2004)
> Running w/Sleepycat Software: Berkeley DB 4.3.27: (Dec
Hi,
--On 18. Januar 2005 17:12:39 Uhr -0200 Andreas Hasenack
<[EMAIL PROTECTED]> wrote:
For some reason the file /var/lib/imap/db/log.001081 belonged to
root! I am pretty sure that nobody changed the ownership manually. Is
this a
Seems someone ran recover (either db_recover or cyrus' recover
> On Tue, Jan 18, 2005 at 07:23:53PM +0100, Sebastian Hagedorn wrote:
>> Up to now we haven't had any problems attributable to Berkeley DB,
>> contrary
>> to the experience of several other people. But today the following
>> appeared
>> in our logs:
>>
On Tue, Jan 18, 2005 at 07:23:53PM +0100, Sebastian Hagedorn wrote:
> Up to now we haven't had any problems attributable to Berkeley DB, contrary
> to the experience of several other people. But today the following appeared
> in our logs:
>
> Jan 18 13:16:25 lvr
SASL 2.1.20
Built w/Sleepycat Software: Berkeley DB 4.1.25: (August 21,
2003)
Running w/Sleepycat Software: Berkeley DB 4.1.25: (August 21,
2003)
Built w/OpenSSL 0.9.7a Feb 19 2003
Running w/OpenSSL 0.9.7a Feb 19 2003
CMU Sieve 2.2
Hi,
The documentation at
http://asg.web.cmu.edu/cyrus/download/imapd/install-upgrade.html
says that one can use the command cvt_cyrusdb to convert Cyrus 2.1.x Berkeley
database files to Cyrus 2.2.x skiplist files.
Unfortunately this does not work if Cyrus 2.1.16 is linked against Berkeley
DB
I posted earlier today about a performance issue I'm seeing with
cyrus-imap 2.2.4 (and 2.2.5, I attempted an upgrade)... A basic summary
from before:
- RedHat Enterprise Server 3.0
- Upgrading from Redhat 7.3
- Cyrus 2.2.5
- Upgrading from Cyrus 2.0.16
- Pam auth through sasl, authenticating agai
abase from
Berkeley DB to skiplist.
1. stop the server
2. run db_recover in var/imap/db
3. rm the log file from var/imap/db and any left over __db files
4. cd var/imap/user
5. run a script which for each seen file in every directory did a db_dump
and a db_load
6. repeat steps 2 and 3 at
2004, Mark Keasling wrote:
> Did you try converting all of the ".seen" berkeley db files to skiplist before
> moving them? After stopping cyrus, something like this might work for you:
>
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu
Hi,
Did you try converting all of the ".seen" berkeley db files to skiplist before
moving them? After stopping cyrus, something like this might work for you:
cd var/user
for f in */*.seen
do
cvt_cyrusdb `pwd`/$f berkeley `pwd`$f.new skiplist
done
Rename
Dear All,
I am running cyrus 2.2.3 on a linux system but at the end of my tether with it.
It is now a live environment with around 20,000 users. At the moment it is
down. I have discovered that Berkeley DB is utter rubbish and totally
unusable. However, there appears to be no way to get rid of it
Hello,
While I am compailing cyrus-imad 2.2.3 I got following error:
make[1]: *** [cyrusdb_berkeley.o] Error 1
make[1]: Leaving directory `/usr/src/cyrus-imapd-2.2.3/lib'
make: *** [all] Error 1
Can somebody help me with this ?
Thx
Bartosz
---
Home Page: http://asg.web.cmu.edu/cyrus
Wiki/FAQ: h
Hi all,
What is the current feeling on the best Berkeley DB version to use with
Cyrus IMAP 2.2.3? In the past there had been some problems with 4.x, but
it appears that many (most) people are using 4.1.x, and there is now
support for 4.2.
What is CMU using?
Thanks.
-David
David R Bosso
On Thu, Dec 18, 2003 at 03:17:35PM -0500, Igor Brezac wrote:
> It seems pretty solid in my limited testing. I have rebuild all apps
> depending on DBD and I have not had any problems. I have not done
> performance testing yet.
Same here, I use cyrus-imapd localhost so that I can test several
ema
On Thu, 18 Dec 2003, Amos Gouaux wrote:
> >>>>> On Mon, 15 Dec 2003 10:55:34 -0200,
> >>>>> Andreas <[EMAIL PROTECTED]> (a) writes:
>
> a> Has anybody tried to compile cyrus-imapd-2.1.16 with berkeley db 4.2.52?
> a> Should it work?
>>>>> On Mon, 15 Dec 2003 10:55:34 -0200,
>>>>> Andreas <[EMAIL PROTECTED]> (a) writes:
a> Has anybody tried to compile cyrus-imapd-2.1.16 with berkeley db 4.2.52?
a> Should it work?
So, what are folks' impressions of BDB 4.2.52 so far? Does it seem
to be pretty solid?
--
Amos
On Mon, Dec 15, 2003 at 10:14:02AM -0500, Igor Brezac wrote:
> Yes. I failed to mention this. This is a patch applied to cyrus-imapd
> 2.2 and it should work in 2.1.16.
> https://bugzilla.andrew.cmu.edu/cgi-bin/cvsweb.cgi/src/cyrus/lib/cyrusdb_berkeley.c.diff?r1=1.2&r2=1.3
Thanks.
I forgot about
On Mon, 15 Dec 2003, Andreas wrote:
> On Mon, Dec 15, 2003 at 08:26:29AM -0500, Igor Brezac wrote:
> >
> > On Mon, 15 Dec 2003, Andreas wrote:
> >
> > > Has anybody tried to compile cyrus-imapd-2.1.16 with berkeley db 4.2.52?
> > > Should it work?
> >
On Mon, Dec 15, 2003 at 08:26:29AM -0500, Igor Brezac wrote:
>
> On Mon, 15 Dec 2003, Andreas wrote:
>
> > Has anybody tried to compile cyrus-imapd-2.1.16 with berkeley db 4.2.52?
> > Should it work?
>
> It should work assuming configure script can locate berkeley
On Mon, 15 Dec 2003, Andreas wrote:
> Has anybody tried to compile cyrus-imapd-2.1.16 with berkeley db 4.2.52?
> Should it work?
It should work assuming configure script can locate berkeley db 4.2.52. I
have cyrus imapd 2.2 working with berkeley db 4.2.52. I believe the
berkeley code i
Has anybody tried to compile cyrus-imapd-2.1.16 with berkeley db 4.2.52?
Should it work?
Hello,
as more and more freebsd packages now are compiled with berkeley db 4.1
i also want to recompile cyrus-imapd with this newer one.
Will my installation continue to work?. Which *.db files should i dump
and restore?
--
Mit freundlichen Grüßen
Fritz Heinrichmeyer FernUniversitaet, LG ES
I just committed some changes to the Berkeley DB configuration subsystem
to the Cyrus 2.1 branch of CVS.
If some of the people who generally have Berkeley DB troubles with Cyrus
could test it out and let me know, that'd be great.
It should be much closer to how SASL works now, which whil
On Wed, 23 Oct 2002 at 15:55 Aidan Evans wrote to Info Cyrus, Rob...
>On Sat, 19 Oct 2002 at 10:49 Rob Siemborski wrote to Aidan Evans and Info Cyrus
>
>>On Sat, 19 Oct 2002, Aidan Evans wrote:
>...
>>> My experience with DB 4.0.14 on RedHat Linux 7.2 is two instances of
>>> complete failure of
On Wed, 23 Oct 2002, Aidan Evans wrote:
> Does CMU have a regular Cyrus shutdown/restart and/or regular reboot of
> the machine running Cyrus? Rebooting certainly resets the lock count; I
> don't know if just a Cyrus restart is enough but I suspect not.
I suppose that depends on what you mean
On Sat, 19 Oct 2002 at 10:49 Rob Siemborski wrote to Aidan Evans and Info Cyrus
>On Sat, 19 Oct 2002, Aidan Evans wrote:
...
>> My experience with DB 4.0.14 on RedHat Linux 7.2 is two instances of
>> complete failure of deliver.db and tls_sessions.db (and consequently all
>> Sieve processing) wh
On Sat, 19 Oct 2002, Aidan Evans wrote:
> What Berkeley DB is CMU using? I assume this is on Solaris, so it may
> not be safe to compare to use on Linux. Whatever version it is, it
> certainly sounds as though it works for CMU.
4.0.14, but we're only using it for the TLS
I upgraded to Berkeley 4.1.24 and now the whole installation does not
work. I made ctl_cyrusdb -r but that does not fix it. What can I do
either! I really need the mailserver working again as soon as possible.
Its a "never change a running system" thing but now many people dont
have email today
Hi,
On Thu, 17 Oct 2002 09:10:44 -0400 (EDT), Rob Siemborski <[EMAIL PROTECTED]> wrote...
> On Thu, 17 Oct 2002, Mark Keasling wrote:
>
> > I'm trying to use Berkeley DB 4.0.14 and am getting the dreaded
> > DBERROR db4: 4 lockers
> > messages even when
t_hoe
Envoyé : jeudi 17 octobre 2002 14:01
À : [EMAIL PROTECTED]
Objet : Re: Is using Berkeley DB 4.0.14 recommended?
At 13:27 17.10.2002 +0200, Simon Matter wrote:
>Mark Keasling schrieb:
>>
>> Hi,
>>
>> I'm trying to use Berkeley DB 4.0.14 and am getting th
On Thu, 17 Oct 2002, Mark Keasling wrote:
> I'm trying to use Berkeley DB 4.0.14 and am getting the dreaded
> DBERROR db4: 4 lockers
> messages even when only starting up the master process. From
> what I've seen reported, the lockers number will only increase and
> cy
At 13:27 17.10.2002 +0200, Simon Matter wrote:
>Mark Keasling schrieb:
>>
>> Hi,
>>
>> I'm trying to use Berkeley DB 4.0.14 and am getting the dreaded
>> DBERROR db4: 4 lockers
>> messages even when only starting up the master process. From
>>
Mark Keasling schrieb:
>
> Hi,
>
> I'm trying to use Berkeley DB 4.0.14 and am getting the dreaded
> DBERROR db4: 4 lockers
> messages even when only starting up the master process. From
> what I've seen reported, the lockers number will only increase and
> c
Hi,
I'm trying to use Berkeley DB 4.0.14 and am getting the dreaded
DBERROR db4: 4 lockers
messages even when only starting up the master process. From
what I've seen reported, the lockers number will only increase and
cyrus will eventually start failing.
Is it recommended to:
r
m: Scott Russell <[EMAIL PROTECTED]>
>>[...]
>> While testing Cyrus IMAPd 2.1.9 I noticed these errors in my logs:
>>
>> Sep 11 17:23:55 ogg lmtpd[773]: DBERROR db3: 16 lockers
>...
>>Berkeley db 4.0 has a bug where the number of lockers isn't
>>decre
Aidan Evans schrieb:
>
> We're using Berkeley DB 4.0.14 for deliver.db and tls_sessions.db and for
> the second time in a couple of weeks both of these databases are
> non-functional because of "Lock table is out of available locker entries".
>
> This err
We're using Berkeley DB 4.0.14 for deliver.db and tls_sessions.db and for
the second time in a couple of weeks both of these databases are
non-functional because of "Lock table is out of available locker entries".
This error may be caused by a bug that is fixed as des
I you are trying to use Berkeley DB 4.0 (and likely 3.3) on Mac OS X,
you will need the following patch or the mutexes will not work and you
will eventually encounter database corruption.
-kevin
I believe the appended patch
will make Berkeley DB run correctly on your Mac OS X system.
Please
Ken Murchison wrote:
>
> Olaf Zaplinski wrote:
>
>>Clifford Thurber wrote:
>>
>>>What do you mean when you say they don't disappear? Can you be more
>>>specific?
>>
>>Yes, right now I have 5 processes named 'imapd -s' and 2 named 'lmtp' in my
>>process list. They will stay there forever until I
Olaf Zaplinski wrote:
>
> Clifford Thurber wrote:
> > What do you mean when you say they don't disappear? Can you be more
> > specific?
>
> Yes, right now I have 5 processes named 'imapd -s' and 2 named 'lmtp' in my
> process list. They will stay there forever until I restart cyrus-imapd. And
Clifford Thurber wrote:
> What do you mean when you say they don't disappear? Can you be more
> specific?
Yes, right now I have 5 processes named 'imapd -s' and 2 named 'lmtp' in my
process list. They will stay there forever until I restart cyrus-imapd. And
when the first user logons after tha
Now it works - in /usr/include, I had to delete db.h and the db3 directory.
But my problem is not resolved: I still have several imapd and sometimes one
or more lmtp processes which never disappear.
Olaf
PROTECTED]
Subject: RE: bug in imapd-2.1.3 / Berkeley DB
Perhaps all this could be made into a nice Linux how to as the current one
seems rather dated and doesn't address any of these problems.
At 11:37 AM 3/26/2002 -0500, OCNS Consulting wrote:
>Clifford:
>
>You are correct! The only wa
>object file: No such file or directory
>
>I don't know what impact this may or may not have but given the reference to
>"libsasl"
>there appears to be some authentication ramification's). Does anyone know?
>
>RB
>
>-Original Message-
>From:
uot;libsasl"
there appears to be some authentication ramification's). Does anyone know?
RB
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Clifford
Thurber
Sent: Tuesday, March 26, 2002 10:32 AM
To: Prune
Cc: Olaf Zaplinski; [EMAIL PROTECTED]
;1.
>>>CPPFLAGS=-I/usr/local/BerkeleyDB.3.3/include \
>>>LDFLAGS=-L/usr/local/BerkeleyDB.3.3/lib \
>>>./configure
>>>
>>>2.
>>>make
>>>
>>>3.
>>>make install
>>>
>>>4.
>>>start of cyrus =>
figure
>>
>> 2.
>> make
>>
>> 3.
>> make install
>>
>> 4.
>> start of cyrus => 'incorrect version of Berkeley db: compiled against
>> 3.1.17, linked against 3.3.11'
>>
>> So I re-started 3. and voila:
>> gcc -c -I/us
>
>2.
>make
>
>3.
>make install
>
>4.
>start of cyrus => 'incorrect version of Berkeley db: compiled against
>3.1.17, linked against 3.3.11'
>
>So I re-started 3. and voila:
>gcc -c -I/usr/include/db3 -I/usr/local/BerkeleyDB.3.3/include [...]
&g
B.3.3/include \
> LDFLAGS=-L/usr/local/BerkeleyDB.3.3/lib \
> ./configure
>
> 2.
> make
>
> 3.
> make install
>
> 4.
> start of cyrus => 'incorrect version of Berkeley db: compiled against
> 3.1.17, linked against 3.3.11'
>
> So I r
Hi Prune,
Prune wrote:
> can you add the result of the 'configure' ? look at the begining when it
> tests for gcc
do you mean this?
checking whether the C compiler (gcc -I/usr/local/BerkeleyDB.3.3/include
-L/usr/local/BerkeleyDB.3.3/lib) works... yes
checking whether the C compiler (gcc -I/us
Hi *,
following bug occured:
1.
CPPFLAGS=-I/usr/local/BerkeleyDB.3.3/include \
LDFLAGS=-L/usr/local/BerkeleyDB.3.3/lib \
./configure
2.
make
3.
make install
4.
start of cyrus => 'incorrect version of Berkeley db: compiled against
3.1.17, linked against 3.3.11'
So I re-started
r 19 23:23:23 birdbrain tls_prune[25259]: incorrect version of Berkeley
db: co
mpiled against 4.0.14, linked against 3.1.14
Here is how I am compiling cyrus.
CPPFLAGS=-I/usr/local/BerkeleyDB.4.0/include LDFLAGS="-L
/usr/local/BerkeleyDB.4.0/lib -R/usr/local/BerkeleyDB.4.0/lib" ./config
Hi,
I have a question on the way to use Berkeley db in Cyrus.
As you may see, some body posted on a problem that imapd hung.
I found it several times whenever massively testing Cyrus with
postfix/smtpstone with '-L' (lmtp) option.
I think it would be a locking problem caused by B
From: "Esh, Thomas D (Tom)" <[EMAIL PROTECTED]>
Date: Mon, 19 Nov 2001 10:26:22 -0500
We are evaluating the possibility of using cyrus for a
commercial product.
Therefore, I'm looking licensing issues with Cyrus and the Berkeley DB
product must be licens
Esh, Thomas D (Tom) schrieb am Mon, Nov 19, 2001 at 10:26:22AM -0500:
*
* We are evaluating the possibility of using cyrus for a
* commercial product.
*
* Therefore, I'm looking licensing issues with Cyrus and the Berkeley DB
* product must be licensed if the source code of the product
*
We are evaluating the possibility of using cyrus for a
commercial product.
Therefore, I'm looking licensing issues with Cyrus and the Berkeley DB
product must be licensed if the source code of the product
using it is not provided. The license depends on which
Berkeley DB product you are
Does this new Berk DB offer significant improvements for Cyrus?
Anything with this release that Cyrus will be able to take advantage
of at some point?
--
Amos
On Thursday, May 31, 2001, at 01:29 AM, [EMAIL PROTECTED] wrote:
> Clare West writes:
>>
>> I am (obviously) not very experienced with configure. I need to add a
>> -lpthread. Do I do this with something like:
>
>> % LIBS="-lpthread" ./configure
>
> Please report the configure bug. Here's
1 - 100 of 107 matches
Mail list logo
