home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.aix
- Path: sparky!uunet!ukma!asuvax!ncar!uchinews!msuinfo!convex.cl.msu.edu!boone
- From: boone@convex.cl.msu.edu (Dennis Boone)
- Subject: Re: Virtual Memory curiosity
- Message-ID: <1992Nov18.193645.11129@msuinfo.cl.msu.edu>
- Keywords: VM overflow response
- Sender: news@msuinfo.cl.msu.edu
- Organization: Michigan State University, East Lansing
- References: <bmarlowe.721422470@ka> <1992Nov12.131230.130467@jrh.uucp>
- Distribution: usa
- Date: Wed, 18 Nov 92 19:36:45 GMT
- Lines: 24
-
- In article <1992Nov12.131230.130467@jrh.uucp> jrh@jrh.uucp (James R. Hamilton) writes:
- >In article <bmarlowe.721422470@ka> bmarlowe@ka.reg.uci.edu (Brett Marlowe) writes:
- >>I've heard rumor that AIX will pick processes to kill off to avoid
- >>running out of virtual memory? Can anyone verify this and if this is
- >>true a) is there a way to disable this "feature" and b) what idiot
- >>decided that randomly killing processes was a good idea??!!
- >>
- > It is true that AIX will start killing process when it runs out of
- > page space. You can disable this feature (i.e. protect a process)
- > by it calling "signal(SIGDANGER, SIG_IGN)". WRT to the idiot that
- > decided to randomly kill processes, the decision is not random --
- > processes are killed youngest first (in AIX 3.2) and if they ignore
- > SIGDANGER then they are not killed at all.
-
- I tend to agree with Brett. The solution is completely non-portable and
- non-standard, so out-of-the-box software has to be modified. You can't
- run a stable system if the o/s is going to run around whacking off
- important processes. The fact that the decision isn't really random makes
- no difference: it still isn't possible to tell which processes will get
- the axe without keeping continuous track of every new process.
-
- Dennis
- --
- = There is no monopoly on common sense, on either side of the political fence =
-