We have a process running on one of our systems that runs consistently for
approx 20 minutes before completing and logging the fact that it received a
SIGHUP signal. The process is used to gether information from an Oracle
database and format this into a flat file report.
I am wondering if there are any user / process restrictions that might be
causing this behaviour?
When a users process exceeds some kernel defined limit, how does the kernel
stop the process?
Is this likely to be related to any O/S configured limits?
Still investigating...
Mat
butlergm_at_logica.com
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
Received on Mon Oct 21 2002 - 01:17:26 NZDT