This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: last snapshot (2011-03-13)
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 18 Mar 2011 17:20:30 +0100
- Subject: Re: last snapshot (2011-03-13)
- References: <20110318120317.67248pzjnhm9gwz9@messagerie.si.c-s.fr>
- Reply-to: cygwin at cygwin dot com
On Mar 18 12:03, EXCOFFIER Denis wrote:
> This message follows http://cygwin.com/ml/cygwin/2011-03/msg00539.html
>
>
> Both system are
> Microsoft Windows XP Professional Version 2002 Service Pack 3.
>
> The system that produces the "File too large" error is:
> Intel(R) Core(TM)2 Duo CPU
> E6850 @ 3.00GHz
> 3.00 GHz, 3.48 GB of RAM
>
> The system where i'm unable to obtain the message is:
> Intel(R) Core(TM)2 Duo CPU
> T9600 @ 2.80GHz
> 2.79 GHz, 1.97 GB of RAM
Maybe it has something to do with the nonpaged pool size? MSDN states:
"Every time a named pipe is created, the system creates the inbound
and/or outbound buffers using nonpaged pool, which is the physical
memory used by the kernel. [...]
The input and output buffer sizes are advisory. The actual buffer
size reserved for each end of the named pipe is either the system
default, the system minimum or maximum, or the specified size rounded
up to the next allocation boundary. The buffer size specified should
be small enough that your process will not run out of nonpaged pool,
but large enough to accommodate typical requests."
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple