Re: [courier-users] Apache file descriptors [was: Re: Problems with

This is a discussion on Re: [courier-users] Apache file descriptors [was: Re: Problems with within the Courier-Imap forums, part of the Mail Servers and Related category; Bernd Wurst wrote: > Am Mittwoch, 13. Februar 2008 schrieb Gordon Messmer: > >> If it's a Red ...


Go Back   Usenet Forums > Mail Servers and Related > Courier-Imap

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 02-15-2008
Gordon Messmer
 
Posts: n/a
Default Re: [courier-users] Apache file descriptors [was: Re: Problems with

Bernd Wurst wrote:
> Am Mittwoch, 13. Februar 2008 schrieb Gordon Messmer:
>
>> If it's a Red Hat or similar system, I'd recommend putting:
>> ulimit -n 2046
>> in /etc/sysconfig/httpd. Otherwise, add it to your httpd init script
>> (and beware of updates that might overwrite your local modifications).
>>

>
> We have had this before but it does not work.
>
> It worked for log files but FastCGI-sockets and the given courier problems
> persisted.
> The apache error message changed, it did not complain about file descriptor
> limit but about a file descriptor number above "FD_SETSIZE".
> I don't know internals of this. :)
>


If you look around, you can find documentation on increasing that limit,
but that's well outside the scope of this list. :)

This is a halfway decent outline of what needs to be done:
http://kb.swsoft.com/en/260

However, I wouldn't use pbone or rpmfind. Get the src.rpm packages
directly from your vendor. Also, avoid using "--force" with rpm. Use
"--replacefiles --replacepkgs" instead. Using "--force" may mask other
problems, such as dependencies, that will cause the package not to
function after you install it.

Once you take these steps, you'll be personally responsible for your
updates. You'll need to make absolutely certain that you never patch
your system until you've checked that the updates aren't for packages
that you've rebuilt, and updated those with local version first. It'll
probably be a lot of extra work.

With all of that said, I personally think that the right thing to do is
not to do per-domain log file at all. Instead, use a LogFormat that
includes the virtual host's name, and sort the log files out afterward.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users
Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 06:41 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0