Some random rambling on this topic. I'm not sure I'm contributing a whole
lot new.
In general, distributed filesystems are nice mechanisms for doing general
purpose stuff. However, when you try to layer very specific tasks on top
of distributed filesystem, you may run into problems where you
--On Tuesday, March 19, 2002 6:29 PM +0200 [EMAIL PROTECTED]
wrote:
> Here is the idea:
>
>
>
> CyrusBox1 CyrusBox2
> \ /
>`-\__/
> SAN
>
>
>
> The questions are:
> 1) Can it be done
The main reason not to use sasldb is that we don't provide many
administration tools -- so users changing their password requires
additional software.
However, this isn't advocating using ldap. The main reason for using ldap
is because it is already there. If you don't already have ldap up, I'
We rolled out the skiplist backend on Saturday and it could hae gone a
little better. For some reason, it seems that the performance of
fdatasync() under Solaris 2.7 is terrible under high load conditions or
maybe we're just assuming the operating system is smarter than it actually
is (or mayb
Both your messages to cyrus-bugs were replied to. In fact, the first one
was replied to within 12 hours and the second within 10 minutes.
Second, unless you are dropping most of the messages from this list too,
you'll also see that there are a number of people that have this working.
Third, th
"Andres Maduro" <[EMAIL PROTECTED]> writes:
> Thanks for your message. After modifying the hashing code, how should I
> configure multiple partitions ? I checked the manual for imapd.conf but
> don't understand exactly how this is accomplished.
See doc/overview.html.
The hashing code is applie
> Feb 24 22:45:54 mail imapd[22212]: IOERROR: creating directory
> /var/spool/imap/user/0132123: Too many links
It looks like the problem is that ext3 won't let you create that many
directories in one directory.
Take a look at the hashimapspool option. When you modified the code to
accep
With the release of Cyrus IMAP 2.1.2 there will be a new backend option:
skiplist.
We have already moved our development system to use it and performance
seems very good. I expect we'll be moving our production system to it
within a few months. It should not suffer from the same problems with
Susan,
I'm sorry but we are not going to change the server because a vendor
thinks that a bug in their code requires us to change perfectly
correct code. We disagree with their belief that a robust MIME parser
is one that works around their bugs and do not consider this change an
enhancement of
We had some problems but as has been indicated lately, things should
be back to normal.
Walter
For some reason we have not had any performance problems, especially
after upgrading to 2.0.16. Our config is described at
http://asg.web.cmu.edu/cyrus/config.html.
We consistently saw over 3000 imapds during the summer and now we are
typically seeing around 5500 imapds. (This also doesn't count
The point is that you can come up with an infinite number of
vulnerabilities as a result of misconfiguration.
The second point is that you can not assert sasldauthd/pwcheck creates
denial of service attacks or is insecure without considering the
services that uses it.
Walter
Devdas Bhagat <[EMAIL PROTECTED]> writes:
>
> The current implementation of SASL does not support remote
> connectivity.
I believe the basic problem is that you don't see where SASL fits
in. Your comment is much like saying that you can't use an orange to
chew gum.
> What most people are looki
re: doc updates.
Part of the problem is that people are distributing binaries without
the source code and all the docs are in the doc/ subdir of the source
distribution.
I'm not sure what Sourceforge would add for us. I believe we've
applied most of the documentation changes sent our way. We jus
Spark <[EMAIL PROTECTED]> writes:
> Maybe somebody can comeup with change to the code that can implement this??
ok, the change is in cvs. I also included a diff below.
Please let us know if this makes things any better (or worse).
Walter
Helmut Apfelholz <[EMAIL PROTECTED]> writes:
> this is greate that the development of the server is
> moving along. I hope that you guys at cmu also watch
> to mailing list, and have seen the 'forking problem' that
> ppl here have been describing.
Yes, we read the mailing lists but have been bus
"Barbara Greenwood" <[EMAIL PROTECTED]> writes:
> The next most highly loaded box is the one running Cyrus (a beefy PC
> running FreeBSD, BTW), at the busiest time it is running at 50% CPU
> utilisation and is not disk-bound.
What is your connection rate? It could be that you are forking off a
wh
"Grant Beattie" <[EMAIL PROTECTED]> writes:
> Is Cyrus safe to use on a logging file system?
It should be safe. The basic thing is that if the operating system
tells the application that data has been committed to disk, then you
need to be able to assume that the data is now recoverable even if
=?iso-8859-1?Q?=D8rnulf?= Nielsen <[EMAIL PROTECTED]> writes:
> 1. Does Cyrus IMAPd still rely on the CMU implementation of AgentX or is
> it possible to use net-snmp (Previously known as "ucd-snmp").
Yes, you can use net-snmp. We are using that now ourselves.
The code in the snmp/ directory is
"Tony Johnson" <[EMAIL PROTECTED]> writes:
> CMU uses Solaris 7? I think I read that somewhere.
http://asg.web.cmu.edu/cyrus/config.html
> I'd be interested to know if they had to patch thier own code or if
> they just did:
> ./configure (options)
> make all
> make install
We do not patch o
You shouldn't be looking at PAM and LDAP with Windows 2000. Windows
2000 provides Kerberos 5 server as part of Active Directory.
If you have any clients that support K5, you can just use the GSSAPI
plugin.
The plain text password checking against Kerberos 5 is in CVS for SASL
as part of libsasl
Ken Murchison <[EMAIL PROTECTED]> writes:
> I know there are lots of other people using PAM, and I for one would
> hate to see support for it taken out of SASL.
The idea is to simplify the case where you are given a plaintext
password and need to authenticate with it. PAM support isn't really
bei
Jeremy Beker <[EMAIL PROTECTED]> writes:
> Dec 27 07:34:51 blackops lmtpd[28232]: DBERROR db3:
> /var/imap/db/__db.003: Too many open files in system
> Dec 27 07:34:52 blackops lmtpd[28232]: DBERROR: dbenv->open
> '/var/imap/db' failed: Too many open files in system
What OS are you ru
We currently just dump the filesystem using Amanda. We have a 21 day
rotation.
In the future, what we would like to do is basically map the concept
of AFS volume to IMAP folders. Specifically, this means that we'd like
to have
a) OldFiles - a read-only view of your mailbox from some time
"Erin B. Peszko" <[EMAIL PROTECTED]> writes:
> We're experiencing the problem of our /var/imap partition filling up (to
> 100% capacity) very quickly, typically during the day where there may be
> around 3000 imapd processes running. We're suspecting that there needs to
> be a 'close mailboxes' in
Stefano Santoro <[EMAIL PROTECTED]> writes:
> I am not looking for scientific numbers, but I would like
> to get an estimate of how many concurrent cyrus imapd
> connection I can achieve with a dual 800 Mhz PIII, 1GB,
> 20GB+ storage on 80MB+ SCSI linux server.
Anywhere from 1000-3000 imapds.
De
Amos Gouaux <[EMAIL PROTECTED]> writes:
> It's not available yet, is it?
I'm sure it won't come as a shock that it is available and functional
but we are lagging behind on documentation.
As a side note, we're going to be putting into production the
aggregator with the 2.x codebase at the end of
Walter Steiner <[EMAIL PROTECTED]> writes:
> > 2.0.7 is pretty stable. The CVS version fixes a couple of little bugs. If
>
> does anybody know when to expect the release of 2.0.8 (or whatever it
> will be)?
Very soon (probably within a week). If anyone is holding on to any
patches, now would b
28 matches
Mail list logo
