On Wed, 2003-01-15 at 13:12, Tom Parquette wrote:
> Lowell Gilbert wrote:
> > Tom Parquette <[EMAIL PROTECTED]> writes:
> > 
> > 
> >>I'm getting an "Out of memory!" message from the mirror
> >>(/usr/ports/ftp/mirror-2.9) port trying to update a large archive.
> >>I've tried a number of things but I can't resolve this.
> >>Any suggestions?
> > 
> > 
> > hitting a limits(1) limit?
> > 
> Lowell,
> I've been playing with this on and off for a few days.
> Your question, I think, put me onto something.
> I've been rerunning the mirror command with top running.
> mirror fails with the memory size around 520m consistantly.
> Limits gives me a datasize limit of 524288kb.  (Close enough for me!)
> I've come to the conclusion that the man page would benefit from some 
> examples.  I've been trying to raise the datasize limit but it does not 
> seem to take.
> 
> Example: limits -B -d 4g mirror.sh... still blows up with memory values, 
> from top, around 520m (give or take a little.)
> 
> You've gotten me looking in the right area.  All I have to do now is get 
> the override to work.  Can anybody provide any insights on how to 
> actually do this?
> Cheers...

I've hit this with really large MySQL databases, and rsyncing massive
directory structures.

You've got to set your maximum data size higher. You can set this in the
kernel config, or do it at startup (no need to recompile that way). Edit
or create the file /boot/loader.conf and add this line:

kern.maxdsiz="2147483647"

That will give you 2G to play with instead of 512M. (If you need more
than that, you might start running into problems.)
-- 

The information contained in this email is confidential.
If you are not the intended recipient, you may not disclose or use the
information in this email in any way.
Dark Blue Sea does not guarantee the integrity of any emails or attached
files.
The views or opinions expressed are the author's own and may not reflect
the views or opinions of Dark Blue Sea.
Dark Blue Sea does not warrant that any attachments are free from
viruses or other defects.
You assume all liability for any loss, damage or other consequences
which may arise from opening or using the attachments.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Reply via email to