On Friday 07 April 2006 13:05, Philip Hazel wrote: > Quote from spec.txt, from the description of split_spool_directory: > > When split_spool_directory is set, the behaviour of queue runner > processes changes. Instead of creating a list of all messages in the > queue, and then trying to deliver each one in turn, it constructs a > list of those in one sub-directory and tries to deliver them, before > moving on to the next sub-directory. The sub-directories are processed > in a random order. This spreads out the scanning of the input > directories, and uses less memory. It is particularly beneficial when > there are lots of messages on the queue. However, if > queue_run_in_order is set, none of this new processing happens. The > entire queue has to be scanned and sorted before any deliveries can > start.
Ahh, I hadn't read that yet. What I remembered was in section 3.6: By default all these message files are helf in a single directory called input inside the general Exim spool directory. Some operating systems do not perform very well if the number of files in a directory gets very large; to improve performance in such cases, the split_spool_directory option can be used. This causes Exim to split up the input files into 62 sub-directories whose names are single letters or digits. While that doesn't directly contradict the above, it makes things a bit unclear... Sorry for the misunderstanding. Cheers, -- Casey Allen Shobe | [EMAIL PROTECTED] | 206-381-2800 SeattleServer.com, Inc. | http://www.seattleserver.com -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
