This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Using large memory segments with a telnet session
- To: "'cygwin at cygwin dot com'" <cygwin at cygwin dot com>
- Subject: Using large memory segments with a telnet session
- From: "Rist, Mark J." <mark_j_rist at md dot northgrum dot com>
- Date: Thu, 4 Jan 2001 06:53:46 -0800
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