On Mon, 28 Oct 2002 at 21:47:27 -0700, Karen Barnes wrote: > [karen@localhost]$ ulimit -a > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > file size (blocks, -f) unlimited > max locked memory (kbytes, -l) unlimited > max memory size (kbytes, -m) unlimited > open files (-n) 1024 > pipe size (512 bytes, -p) 8 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 7168 > virtual memory (kbytes, -v) unlimited
What i was looking for was the setting of "open files" on the off chance that it was set too low i.e. high enough to start up yet too low such that when all threads start to do work some are occasionally unable to obtain descriptors. 1024 should be plenty but also check that file-max is of reasonable size if you have other descriptor intensive applications running. You can check this with either of 'sysctl -n fs.file-max' or 'cat /proc/sys/fs/file-max'. You say you are getting connect errors. What exactly are the errors i.e. you should see output from index like: Can't connect to host: foo (x.x.x.x): bar What are the "bar"'s in your case (it will be "Too many open files" if the above is the problem). Also check your setting of MinDelay, are your sure your not hammering the remote sites such that they begin to refuse connections? Matt.
