eventalarm.c return code 6

I am using Art's eventalarm.c program on IDS 9.4UC5. The program always return code 6. Is this normal? 10:13:19 Process exited with return code 6: /bin/sh /bin/sh -c /u/informix/etc/eventalarm 2 23 "Logical Log 8415 Complete, timestamp: 0x3f8d49d9." "Logical Log 8415 Thanks Gary Quiring

On Wed, 17 Nov 2004 10:33:33 -0500, Gary Quiring wrote: If you look in the log file (eventalarm.log in the directory named on line 2 of the config file or the directory that was current if not specified when the engine started up) error code 6 indicates that the lock file could not be created. Most likely permissions on the directory that's configured for the lock file in the config file ($INFORMIXDIR/eventalarm.cfg). The lock file, event.S<severity>.C<event class>, is written to the directory in which the engine started. It is created for certain repeated events to prevent multiple mail messages from being sent about the same event within a short period of time (a lock table overflow event could potentially become a denial of service attack otherwise ;-( ) Art S. Kagel > I am using Art's eventalarm.c program on IDS 9.4UC5. The program always > return code 6. Is this normal? > > 10:13:19 Process exited with return code 6: /bin/sh /bin/sh -c> /u/informix/etc/ eventalarm 2 23 "Logical Log 8415 Complete, timestamp: > 0x3f8d49d9." "Logical Log 8415 > > > Thanks > Gary Quiring

On Wed, 17 Nov 2004 16:59:23 -0500, "Art S. Kagel" <kagel@bloomberg.net> wrote: >On Wed, 17 Nov 2004 10:33:33 -0500, Gary Quiring wrote: > >If you look in the log file (eventalarm.log in the directory named on line 2 >of the config file or the directory that was current if not specified when the >engine started up) error code 6 indicates that the lock file could not be >created. Most likely permissions on the directory that's configured for the >lock file in the config file ($INFORMIXDIR/eventalarm.cfg). The lock file, >event.S<severity>.C<event class>, is written to the directory in which the >engine started. It is created for certain repeated events to prevent multiple >mail messages from being sent about the same event within a short period of >time (a lock table overflow event could potentially become a denial of service >attack otherwise ;-( ) > >Art S. Kagel > Hi Art, There is a log file there with no messages in it. I am loading the engine at boot time. I changed the script in rc2.d to change dirs to the directory where eventalarm sits but the log is not touched. It is owned by informix and has 666 perms. I next brought down the engine and restarted it as user root but it still does not touch the log. The program is working as I have plenty of .gz log files. Thanks Gary