Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Apr 1998 17:24:26 -0400
From:      sbabkin@dcn.att.com
To:        freebsd-hackers@FreeBSD.ORG, dec@phoenix.its.rpi.edu
Subject:   RE: SIGDANGER
Message-ID:  <C50B6FBA632FD111AF0F0000C0AD71EEACDEDD@dcn71.dcn.att.com>

next in thread | raw e-mail | index | archive | help
> ----------
> From: 	David E. Cross[SMTP:dec@phoenix.its.rpi.edu]
> 
> I was recenlty shown AIX's SIGDANGER (33). It is a signal that the
> kernel
> issues to [some] running processes when it gets dangerously low on
> space,
> by default SIGDANGER causes programs to die, freeing up memory, system
> critical processes and server processes woulf be compiled to ignore
> SIGDANGER.  This seems like a very good idea, could it be done in
> FreeBSD?
> I remember someone talking about changing the signal structs to be an
> array of INTs, instead of just an int to accomidate more than 32
> signals. 
> 
I guess, it it not applicable to BSD. If FreeBSD uses the same
space allocation method that is described in the devil book,
it will not allow a process to start if it does not have enough
swap space. On the other hand, AIX does speculate and can end
up with swap space shortage at any point of time, not only in
fork/exec/mmap/sbrk code.

-Serge

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C50B6FBA632FD111AF0F0000C0AD71EEACDEDD>