On Fri, Dec 16, 2011 at 10:26, Henning Brauer wrote:
> it is completely beyond me why some people accept anything else.
Because it fits their needs. Even if there was remote access, it would
hang till someone would notice and use it.
Sometimes would be preferable just to force fix of all inode er
I guess I understand what Sebastien is talking about. I used to make
trips to my cheap serverhosting after power failure too :).Just to
type Y, yes repair those blocks, while system was hanging at boot.
Not very pleasant experience...
On Fri, Dec 16, 2011 at 03:00, Kenneth R Westerback
wrote:
>
Hello Dave,
>
> >> My daemon class is now on 512 files. Removed dovecot class.
> >> I'll try this for a while.
>
> >That's probably the less preferable option. The best way would be to
> leave the
> >dovecot class, make sure the _dovecot user is allocated to that class
> (Nico's
> >post will show
> If you perform a `ps aux` you will see what user dovecot is running as,
> that's
> the user whose class you want to check.
[EMAIL PROTECTED] ~ $sudo ps waxu | grep dovecot
root 26251 0.0 0.2 620 912 ?? Ss15Jan07
0:55.12/usr/local/sbin/dovecot
_dovecot 13219 0.0 0.3 560 1580
Hello Nico,
thanks for quick reply.
Does dovecot actually run under this login class?
I did modify login.conf
# cap_mkdb /etc/login.conf
than kill -HUP "_dovecot_PID"
I hope that's enough to run it under dovecot class. How do I find out?
What does `sysctl kern.maxfiles` say?
$sysctl kern.ma
This kind of message started to fill my log probably month ago:
Mar 12 07:20:08 mail dovecot: pipe() failed: Too many open files
I'm using dovecot on small home mail server 10 users. I thought this is
maybe because I'm using maildir, IMAP
and my daemon did have default openfiles.
I raised openfil
6 matches
Mail list logo
