Mike Tancsa wrote:
At 08:15 PM 7/23/2003 -0700, Kris Kennaway wrote:
On Wed, Jul 23, 2003 at 01:34:27PM -0400, Gabor wrote:
> Here is the tail end of the output. It dies when trying to poke at
> the memory using memset. If I just malloc without the memset, it
> never even dies.
Ah, the annual
At 08:15 PM 7/23/2003 -0700, Kris Kennaway wrote:
On Wed, Jul 23, 2003 at 01:34:27PM -0400, Gabor wrote:
> Here is the tail end of the output. It dies when trying to poke at
> the memory using memset. If I just malloc without the memset, it
> never even dies.
Ah, the annual "memory overcommit" t
On Wed, Jul 23, 2003 at 01:34:27PM -0400, Gabor wrote:
> Here is the tail end of the output. It dies when trying to poke at
> the memory using memset. If I just malloc without the memset, it
> never even dies.
Ah, the annual "memory overcommit" thread. I thought we were overdue
for one.
Kris
I'm trying to do a little system hacking on CMU Lisp. Currently CMU
Lisp has a minimum of two files needed to execute. One is a program
usually called "lisp" that the OS runs, which basically a loader for
the other file, a lisp.core file that contains the actual lisp system.
People have been as
Peter Jeremy wrote:
FreeBSD behaviour in the face of swap shortage is a regular and
popular discussion topic. I suggest that a perusal of the archives
Yes but I for example have had this issue since 2.1-R (when I started
using it), freezing when the system trashes, without hope for resolve,
or
Peter Jeremy wrote:
FreeBSD behaviour in the face of swap shortage is a regular and
popular discussion topic. I suggest that a perusal of the archives
will probably answer any questions. If anyone wishes to suggest a
"solution" to FreeBSD's behaviour when there is a shortage of swap,
please incl
On 2003-Jul-23 15:44:36 -0700, Brooks Davis <[EMAIL PROTECTED]> wrote:
>On Thu, Jul 24, 2003 at 12:36:54AM +0200, Matthias Buelow wrote:
>> Wasn't there a sysctl flag to enable/disable overcommitting?
>> I think I remember something but I can't find it; it might
>> not have been on FreeBSD.
>
>No t
On 23 Jul, Brooks Davis wrote:
> On Thu, Jul 24, 2003 at 12:36:54AM +0200, Matthias Buelow wrote:
>> Barney Wolff writes:
>>
>> >One might argue that this is a config error, and ulimit should be used
>> >to cut the address space to below actually available memory.
>>
>> Wasn't there a sysctl flag
Hi there,
I've installed a Qlogic HBA in a 4.8-STABLE machine and I'm able to present
LUNs to this machine from an HDS array and use them. That all works
perfectly. However, the only time I pick up new LUNs is on a reboot.
Seems like I should be able to rescan the fabric and pick up new LUNs, b
