From: Butler, Mathew (ButlerGM@logica.com)
Date: Tue Oct 29 2002 - 23:29:09 EST
THanks to Dr Thomas Blinn
ANSWER:
The kernel itself is not likely to be the initiator. Do you by
any chance run any kind of "idle process killer"? That would be
a likely culprit.
- We run no such process killer, and the problem is still ongoing. When
resolved I will re-summarise,
ORIGINAL QUESTION:
> 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
>
>
>
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.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:58 EDT