Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Frank Seide" To: Subject: lock down cygwin1.dl in memory to avoid paging in a network installation? Date: Thu, 7 Feb 2002 11:34:29 +0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Hi, does anyone have an idea how to force cygwin1.dll to be loaded entirely and then locked down in physical memory so that NT won't page it out? In our compute server farm, to reduce maintainance overhead, I installed Cygwin UNIX-like "in the network," i.e. the cygwin root (/) and everything below like /bin, /etc etc is on an NT network drive. With this I can "install" Cygwin on any computer by using a single Cygwin-"mount" command, and all "installations" are guaranteed to be identical, works well. However, once the NT file server crashes or falls into meditation or the network hangs for >~1 minute, cygwin does not function anymore reliably. Programs (running or newly started) sooner or later crash with seg fault or STATUS_ACCESS_VIOLATION. It seems the file handle to cygwin1.dll becomes invalid due to a timeout, and subsequent requests for paging in dll code fail. The only way to recover is to terminate _all_ cygwin processes which unloads cygwin1.dll. Our jobs often run many days, and there are multiple cygwin jobs on each multi-CPU server. Anyone any idea? Thanks! Frank -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/