If I use the socket option I can't use the count option to create more
authentication processes. I get this error. Thanks in advance.
dovecot: Jan 25 06:57:04 Error: auth(default): Socket already exists:
/var/run/dovecot/auth-client
auth default {
mechanisms = plain
passdb passwd-file {
# Master users that can log in as anyone
args = /etc/dovecot.masterusers
master = yes
pass =yes
}
# Linuxconf passwd-like file with specified location
passdb passwd-file {
args = /etc/exim/control/vmail/shadow.%d
}
# Linuxconf passwd-like file with specified location
userdb passwd-file {
args = /etc/exim/control/vmail/passwd.%d
}
socket listen {
master {
path = /var/run/dovecot/auth-master
mode = 0666
}
client {
path = /var/run/dovecot/auth-client
mode = 0666
}
}
# Number of authentication processes to create
# count = 10
}
On Fri, 2008-01-25 at 06:59 -0800, Marc Perkel wrote:> If I use the socket option I can't use the count option to create more > authentication processes. I get this error. Thanks in advance. > > dovecot: Jan 25 06:57:04 Error: auth(default): Socket already exists: > /var/run/dovecot/auth-clientRight. This is kind of a design problem which isn't that easy to fix (until v2.0). Do you really need more than count=1? I don't think there's any benefit in having count (much) larger than the number of CPUs in the system, and a count=1 can handle thousands of connections/sec on my system. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20080126/f72b2ab6/attachment-0002.bin>
Timo Sirainen wrote:> On Fri, 2008-01-25 at 06:59 -0800, Marc Perkel wrote: > >> If I use the socket option I can't use the count option to create more >> authentication processes. I get this error. Thanks in advance. >> >> dovecot: Jan 25 06:57:04 Error: auth(default): Socket already exists: >> /var/run/dovecot/auth-client >> > > Right. This is kind of a design problem which isn't that easy to fix > (until v2.0). Do you really need more than count=1? I don't think > there's any benefit in having count (much) larger than the number of > CPUs in the system, and a count=1 can handle thousands of > connections/sec on my system. > >My system isn't that busy but I'm getting really sluggish response from Dovecot. Increasing the count seems to make a significant difference. I can't explain why, but I'm trying to track down why I'm seeing a very sluggish response time when I know I have plenty of computing horsepower and it should be nearly instant.
Timo Sirainen wrote:> On Fri, 2008-01-25 at 06:59 -0800, Marc Perkel wrote: > >> If I use the socket option I can't use the count option to create more >> authentication processes. I get this error. Thanks in advance. >> >> dovecot: Jan 25 06:57:04 Error: auth(default): Socket already exists: >> /var/run/dovecot/auth-client >> > > Right. This is kind of a design problem which isn't that easy to fix > (until v2.0). Do you really need more than count=1? I don't think > there's any benefit in having count (much) larger than the number of > CPUs in the system, and a count=1 can handle thousands of > connections/sec on my system. > >There is situations when more than one socket is needed: for chrooted processes. About year ago I did a lots of tests with different chroot setups (internal chroot/external chrooting). About 10 bugs in dovecot was discovered... most of of them are fixed now. [see old post by me; thanks Timo:))] But final conclusion was - Dovecot currently isn't designed for use in chroot setups. Also "mail_chroot": setting brings up more problems than benefits (unable to use external binaries (sendmail) for bounce messages, plugins don't work as expected etc.). Uldis