Hey all, If you'll recall I mentioned that we're getting issues with our arserverd 'hanging'.
The "AR System 7.0 Configuring" guide indicates that there is a parameter known as "RPC-Non-Blocking-IO" which when set : "Prevents invalid or corrupt packets from temporarily disabling the arserverd service." This sounds like our monkey. Has anyone got any information about using setting and what the 'down' side of using it is? Anyone been forced to turn this on at all???? How does a corrupted packet occur anyway??? (so many questions) All I can get from the doco is : "This parameter enables the AR System on compliant systems to receive remote procedure calls in a non-blocking mode. Without this setting, the server must receive an entire RPC header before processing a different one. With this setting, the system can process multiple headers at the same time. Set this parameter to T (TRUE) and then restart your AR System server to run in RPC non-blocking mode. The default for this parameter is F (FALSE); use the following syntax to set to TRUE: RPC-Non-Blocking-IO: T This functionality is not supported on Windows and Linux operating systems. The advantages of RPC-Non-Blocking-IO mode are as follows: Prevents remote attackers from disabling RPC services. Prevents invalid or corrupt packets from temporarily disabling the arserverd service." Thanks George _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
