Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <C12E8508FB1BD211BDFD00A0C9C75B6102296C63@xcgal005.al.essd.northgrum.com>
From: "Rist, Mark J." <mark_j_rist AT md DOT northgrum DOT com>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: RE: Using large memory segments with a telnet session
Date: Thu, 4 Jan 2001 10:44:36 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain

OK. I figured it out. Sorry to labor all of your mailboxes.

Here is the solution.

1. Set the registry key to increase the memory as the user running 
inetd.
2. Shut down the computer completely.
3. Restart the computer. 

Now everything works fine. The reason I believe this works is that 
the inetd service keeps the cygwin1.dll in memory. This is a dll
setting, so unless you completely shutdown all cygwin applications,
including services so that the dll is cleared from memory,
the new setting will not take effect. 

The flip side of this (I think) is that if you are running any cygwin based 
service and increase or decrease the heap size for this service 
all users of the system will get the benefit of the change in memory
size without setting this on a per user basis.

Mark

	-----Original Message-----
	From:	Rist, Mark J. 
	Sent:	Thursday, January 04, 2001 8:54 AM
	To:	'cygwin AT cygwin DOT com'
	Subject:	Using large memory segments with a telnet session

	Thanks to the archive of this mailing list, I have discovered that
you can 
	use large memory segments with cygwin by modifying the registry key:

	HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin

	and adding the value heap_chunk_in_mb (DWORD set to max memory
amount).

	The problem that I am having is that I am logged into a machine via
telnet using 
	the inetutils. It appears that the registry setting is ignored for
telnet sessions. So 
	I can't run large memory programs when logged in remotely.

	The problem may be exaggerated by the fact that I am using roaming
profiles 
	and the registry for the user I am logging in as is stored remotely.

	I have tried several things to no avail:
	1. Setting HKLM\Software\Cygnus Solutions\Cygwin\heap_chunk_in_mb
	I thought this might work since system wide mount points seem to be
working
	and these are set under HKLM. Didn't work.
	2. Setting HKCU\Software\Cygnus Solutions\Cygwin\heap_chunk_in_mb
for the
	user running the inetd service. Nope.

	I am running out of ideas. I am fairly sure that I can recompile the
cygwin1.dll and 
	change the default heap size to get around this problem, but I would
prefer to
	handle this as a configuration so that I don't have to recompile for
every release.

	Any ideas?

	Thanks

	P.S. Why is the default 128 Mb? This seems ridiculously small.


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple