Aleksander Adamowski wrote:
You're right, unless one configures it to spawn enough processes to
cover some temporary spikes in blocking time - so that new authdaemon
processes temporarily hold incoming queries until the timeous occur or
authentication service is restored.
I don't think that's feasible under the current architecture. IIRC, the
documentation specifically notes that authentication modules need to
process requests in a minimum amount of time in order to avoid refusing
connections to clients.
Off topic, but you could consider using another directory server. The
new Fedora DS is quite good, and stores ACIs as attributes in the
directory. Among other advantages, this ensures that security
settings are replicated like the rest of the data.
I would, if it worked under x86_64.
As far as I know, it does. The site for FDS notes that it is a 32-bit
application, but there's no reason that it shouldn't work. It just
won't use many GB of RAM.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
