From owner-freebsd-hackers Mon Apr 27 13:34:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01333 for freebsd-hackers-outgoing; Mon, 27 Apr 1998 13:34:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01315 for ; Mon, 27 Apr 1998 13:34:38 -0700 (PDT) (envelope-from dec@phoenix.its.rpi.edu) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.8/8.8.7) with SMTP id QAA04531 for ; Mon, 27 Apr 1998 16:34:31 -0400 (EDT) (envelope-from dec@phoenix.its.rpi.edu) Date: Mon, 27 Apr 1998 16:34:31 -0400 (EDT) From: "David E. Cross" To: freebsd-hackers@FreeBSD.ORG Subject: SIGDANGER Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. Thoughts? -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message