home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!ut-emx!ibmchs!auschs!awdprime.austin.ibm.com!scott
- From: scott@austin.ibm.com
- Newsgroups: comp.unix.aix
- Subject: Re: Help Needed - program SIGKILLing itself
- Message-ID: <1992Sep2.172426.29972@awdprime.austin.ibm.com>
- Date: 2 Sep 92 17:24:26 GMT
- References: <BturB1.8Ir@math.uwaterloo.ca>
- Sender: news@awdprime.austin.ibm.com (USENET News)
- Organization: IBM Austin
- Lines: 23
- Originator: scott@porter.austin.ibm.com
-
-
- In article <BturB1.8Ir@math.uwaterloo.ca>, mskucher@math.uwaterloo.ca (Murray S. Kucherawy [MFCF]) writes:
- > I have a program which receives data from stdin and uses it to update
- > the AIX password database using setpwdb, setuserdb, putuserattr,
- > putgroupattr, and all those nice things. However, after a while
- > of this processing, it just stops dead, saying "Killed".
-
- Your program is getting killed due to a low paging space condition. It's
- probably using an invalid pointer and running amuck allocating memory and
- paging space. You can verify this by using the command 'ps vg <pid>' where
- <pid> is the process ID of your process. The value under the heading 'SIZE'
- corresponds to the amount of paging space allocated to the process in 1KB
- blocks. If you see this value growing substantially then your program is
- chewing up all the paging space. You can also run the command 'lsps -a'
- to verify this.
-
- To fix the problem you need to find out why your program is allocating so
- much memory/paging space. If it's not due to a faulty pointer but is
- "normal" behavior for your program then you need to increase the amount of
- paging space in the system using either 'mkps' or 'chps'.
-
- Scott L. Porter IBM PSP Austin / AIX Kernel Development
- Internet: scott@glasnost.austin.ibm.com
-