Folks,
I ran wget (1.9.1) on Debian GNU/Linux to find out how many links my site had,
and after Queue count 66246, maxcount 66247 links, the wget process ran out
of memory. Is there a way to set the persistent state to disk instead of memory
so that all the system memory and cache is not
From: oscaruser
[...] wget (1.9.1) [...]
Wget version 1.10.2 is the current release.
[...] Is there a way to set the persistent state to disk instead of
memory [...]
I believe that there's a new computing concept called virtual
memory which would handle this sort of thing
[EMAIL PROTECTED] wrote:
I ran wget (1.9.1) on Debian GNU/Linux to find out how many links my site had,
and after Queue count 66246, maxcount 66247 links, the wget process ran out of
memory. Is there a way to set the persistent state to disk instead of memory so
that all the system memory and
PURPOSE. See the
GNU General Public License for more details.
Originally written by Hrvoje Niksic [EMAIL PROTECTED].
- Original Message -
From: Mauro Tortonesi [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Out of Memory Error
Date: Thu, 25 May 2006 18:43:33 +0200
[EMAIL
: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Out of Memory Error
Date: Thu, 25 May 2006 16:05:15 -0500 (CDT)
[EMAIL PROTECTED]:
[...] For very big runs, I wouldn't want to convert large amounts =
of disk free space to swap space because that reduces the
usability