home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.wizards
- Path: sparky!uunet!stanford.edu!ames!nsisrv!usenet
- From: fgg@gemini.gsfc.nasa.gov (Frank G. Gomez)
- Subject: SIGKILL'ed before exec()
- Message-ID: <1992Aug27.150427.12902@nsisrv.gsfc.nasa.gov>
- Sender: usenet@nsisrv.gsfc.nasa.gov (Usenet)
- Nntp-Posting-Host: gemini.gsfc.nasa.gov
- Organization: NASA GSFC CDP VLBI
- Date: Thu, 27 Aug 1992 15:04:27 GMT
- Lines: 40
-
- Hello,
-
- We are experiencing a SIGKILL when attempting an exec system call. We
- think it is probably due to some system parameter that needs to be
- increased. This hypothesis is based on the following two passages ...
-
- ------------------------------------------------------------------------
- HP-UX Reference Manual Volume 3, page 669 (signal(5)):
-
- "SIGKILL is sent by the system if an exec(2) system call is
- unsuccessful and the original program has already been deleted"
-
- ------------------------------------------------------------------------
- Bach's "The Design of the UNIX Operating System" page 220, 4th paragraph
- (discussing exec's algorithm):
-
- "After copying the exec parameters to a holding place in the kernel,
- the kernel detaches the old regions of the process using algorithm
- detachreg [ ...... ] At this point the process has no user-level
- context, so any errors that it incurs from now on result in its
- termination, caused by a signal [the SIGKILL]. Such errors include
- running out of space in the kernel region table, attempting to load
- a program whose size exceeds the system limit, attempting to load a
- program whose region addresses overlap, and others."
- ------------------------------------------------------------------------
-
- The important questions appear to be:
-
- 1) What are these 'other' reasons ?
- 2) To which system parameters do the first two above-mentioned
- reasons correspond ?
- 3) Under what circumstances would the third reason occur ?
-
- The machine is an HP 730 at 8.05 with 100 MB of swap. The error has
- occurred even when the process was the only user process running.
-
- Any type of answers to these questions would be greatly appreciated.
-
-
- Frank G. Gomez fgg@gemini.gsfc.nasa.gov
-