Programming

Hi all,
I need some urgent help.
we are using Dynix/ptx V4.5 on i386, have several processes and instances are running on the box round the clock.we increased the processes recently.
We have coded to handle the signals in our programs.
Recently, we noticed most of our processes are recieving SIGTERM signal from the kernel and exiting. we can not ignore this signal and the processes are so critical that we cannot have these down for more than 3 to 4 minutes.

Can you please help me in this,

1) When the kernel generates SIGTERM ?
2) can we ignore this safely ?
3) Is there a way to avoid this ?

Your help is highly appriciated

Thanks in advance
Bhupal

first of all check to see if there is suffiecient disk space. 85% usage, no more than that if you are using a live database with instances.

if you have space and there is no problem with that have a look at the foloowing

<pre>

_lwp_sigredirect _signotifywait (2) - deliver process signals to specific LWPs
_signotifywait _signotifywait (2) - deliver process signals to specific LWPs
gsignal ssignal (3c) - software signals
onintr trap (1) - shell built-in functions to respond to (hardware) signals
sigaddset sigsetops (3c) - manipulate sets of signals
sigblock sigblock (3b) - block signals
sigdelset sigsetops (3c) - manipulate sets of signals
sigemptyset sigsetops (3c) - manipulate sets of signals
sigfillset sigsetops (3c) - manipulate sets of signals
siginterrupt siginterrupt (3b) - allow signals to interrupt functions
sigismember sigsetops (3c) - manipulate sets of signals
sigmask sigblock (3b) - block signals
signal signal (5) - base signals
sigpause sigblock (3b) - block signals
sigpending sigpending (2) - examine signals that are blocked and pending
sigsetmask sigblock (3b) - block signals
sigsetops sigsetops (3c) - manipulate sets of signals
sigtimedwait sigwaitinfo (3r) - wait for queued signals
sigwaitinfo sigwaitinfo (3r) - wait for queued signals
ssignal ssignal (3c) - software signals
td_thr_setsigpending td_thr_setsigpending (3t) - manage thread signals for libthread_db
td_thr_sigsetmask td_thr_setsigpending (3t) - manage thread signals for libthread_db
trap trap (1) - shell built-in functions to respond to (hardware) signals
truss truss (1) - trace system calls and signals

</pre>

You can do a quick man for any one of them and pick the appropriate one.