Jon Ribbens <[EMAIL PROTECTED]> writes: > "Daniel C. Sobral" <[EMAIL PROTECTED]> wrote: > > OTOH, though, FreeBSD's malloc() is very unlikely to return an out > > of memory error. > Why is that? Because FreeBSD overcommits memory. You can allocate (almost) as much memory as you want regardless of how much RAM / swap you have. You won't run into trouble unless you actually try to use too much of it. > What happens if the process hits its resource limits? Malloc() fails with ENOMEM. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: Replacement for grep(1) (part 2) Jon Ribbens
- Re: Replacement for grep(1) (part 2) Chris G. Demetriou
- Re: Replacement for grep(1) (part 2) Doug Rabson
- Re: Replacement for grep(1) (part 2) Jordan K. Hubbard
- Re: Replacement for grep(1) (part 2) Warner Losh
- Re: Replacement for grep(1) (part 2) Ollivier Robert
- Re: Replacement for grep(1) (part 2) Daniel C. Sobral
- Re: Replacement for grep(1) (part 2) Todd Whitesel
- Re: Replacement for grep(1) (part 2) Archie Cobbs
- Re: Replacement for grep(1) (part 2) Warner Losh
- Re: Replacement for grep(1) (part 2) Dag-Erling Smorgrav
- Re: Replacement for grep(1) (part 2) Wes Peters
- Re: Replacement for grep(1) (part 2) Jamie Howard
- Re: Replacement for grep(1) (part 2) Dag-Erling Smorgrav
- Re: Replacement for grep(1) (part 2) Alan Barrett
- Re: Replacement for grep(1) (part 2) Tony Finch