UNIX for Dummies Questions & Answers

Hi,

when I execute a script on unix AIX, I've got an error message:
"Execution[56]: 85328 Signal d'alarme".
If I edit this file with "vi", I ve got the same error after a while (about 1 minute).
If I try with another user I still have the problem.

But if I rename this file, no problem.

My file is called asscron.ksh and it is in the crontab in order to be executed every day at 17H00.

Any idea ??? Thanks

I do not know what exactly is going on.

The error message means that the process received SIGALRM, which is like an alarm clock ringing, saying 'wake up'.

Apparently the asccron.ksh script does not handle signals.

Since you get the same error when you are in vi, it looks like there is another process that is running as a daemon or maybe a detached process that looks for 'asscron' or some very similar file name, then sends a SIGALRM to the process that has the file.

Does the asscron.ksh script create another process?

Edit:

Code:

trap "" ALRM
or
trap "" 14

will stop the process from crashing, if it's added near the top of the script. But you still need to find out what is sending signal.

In fact, this script call a C program.
But what i forgot to say is that, the unix server crash very badly just at the time when the script should have been launched via the cron. then after restart of the server we systematically have the message on the script. (with vi, find, more , ...)

Is there something wrong with the system, which try to say 'hey you forgot to launch the script' and each time we try to access the file an alamr message is generated ??

I don't know for sure, but it seems like there is a process somewhere that is doing something like this:

Code:

findpid=`ps -ef | grep "asscron" | cut -f 2 -d' ' `
kill -14 $findpid

Ok , this thread is over.
There was a lock on this script due to the crash, and the server was sharing disk multibaye with another server and on the reboot something didn't work fine. So the lock was on the other server and every time we wanted to access the script an alarm message appeared.
So after deleting locks on the other server and reboot the server everything is fine.

*Thanks for all
Regards.