>>>>> On Tue, 13 Jul 1999 14:53:43 -0700 (PDT),
Matthew Dillon <[EMAIL PROTECTED]> said:
> If you are talking about a user intentionally attempting to run
> a system out of swap, it is fairly easy to do whether the system
> uses an overcommit model or not. The user has any number of
> ways of blowing the server up too - for example, by making
> thousands of connections to it or running many huge queries in
> parallel.
If the kernel and the application behave properly, critical
application doesn't lose it's data in such situation on
non-overcommiting systems.
Your example doesn't make sense.
--
soda
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
- Re: Replacement for grep(1) (part 2) Robert Elz
- Re: Replacement for grep(1) (part 2) Daniel C. Sobral
- Re: Replacement for grep(1) (part 2) Robert Elz
- Re: Replacement for grep(1) (part 2... Matthew Dillon
- Re: Replacement for grep(1) (pa... sthaug
- Re: Replacement for grep(1) (pa... Matthew Dillon
- Re: Replacement for grep(1) (part 2... Daniel C. Sobral
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Noriyuki Soda
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Noriyuki Soda
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2... Noriyuki Soda
- Re: Replacement for grep(1) (pa... Matthew Dillon
- Re: Replacement for grep(1) (pa... Ted Faber
- Re: Replacement for grep(1) (pa... Matthew Dillon
- Re: Replacement for grep(1) (pa... Ted Faber
- Re: Replacement for grep(1) (pa... Kris Kennaway
- Re: Replacement for grep(1) (pa... Gregory Sutter
- Re: Replacement for grep(1) (pa... Mike Smith
- Re: Replacement for grep(1) (pa... Matthew Dillon

