ZXTM FD fix patch
NOTE: This FAQ does not apply to ZXTM 3.1r1 and later.
Leave a comment ...
You can look to see how many concurrent connections each ZXTM thinks it can
handle by looking at "System" -> "Traffic Managers", and then looking under the
"Software" heading for "Concurrency Limit". By default, an untuned Linux
system will read " This document describes one good way to increase this limit on recent Linux kernels (2.6.9 and later).
ZXTM performs best on Linux
... to the " The above tuning will increase the system limit for the absolute total number of File Descriptors that should be usable at any one time, but the per-process limit still needs to be addressed.
This can generally be achieved by editing
--- rc 2005-04-12 19:31:51.912347120 +0100
+++ rc.new2005-04-12 19:32:49.865536896 +0100
@@ -126,8 +126,18 @@
fi
;;
*) ;;
- esac
-
+ esac
+ fdlimit=`ulimit -n`
+ fdnumber=65535
+ if [ $fdlimit = "1024" ]
+ then
+ echo '************************************************************'
+ echo "Warning FD limit is too low ($fdlimit). Attempting to"
+ echo "increase value to $fdnumber."
+ ulimit -n $fdnumber
+ echo "Limit is now `ulimit -n`"
+ echo '************************************************************'
+ fi
}
sendemails()
@@ -153,6 +163,7 @@
;;
'restart')
+ checksysctl
sendemails
stop_pid "$ZXTM_PIDFILE" "$PROGRAM" && \
$ZEUSHOME/zxtm/bin/zeus.zxtm && echo Restarted $PROGRAM
To do this, copy the lines above into a file named With this done, ZXTM will warn you if the default number of available file descriptors is too low, and attempt to raise this level. If you restart ZXTM after applying this patch, you should find that your Concurrency Limit now shows a much higher value. This change is safe to leave in place until the next release of ZXTM, and means that ZXTM can be started unattended without the need for manual intervention.
Stuart Shelton
[Zeus Support] 01 July 2005
|
Recent Articles
Other Resources
|


