Re: alarm handler bug on OWS 7.22?

In article <19981013095206.04001.00000027@ng13.aol.com>, ProzessDV <prozessdv@aol.com> writes >Here is a part of the ONCONFIG file: > ># Diagnostics > >MSGPATH /informix/etc/online.log # System message log file path >CONSOLE /dev/console # System console message path >ALARMPROGRAM db_alarm_prog # Alarm program path> ALARMPROGRAM should be a full path as all other ONCONFIG parameters are. You should not rely on the environment set when it is invoke. Even $PATH is normally minimal when Online runs external commands. E.g. within stored procedures the PATH is even less than that when Online is started!! use Full paths. >The event handler db_alarm_prog is a binary. There is an entry in the variable >path, but I also tried to give the full pathname and the same error ocurred. I >think there is not much I can do wrong in my configuration. I can also show >some entries in online.log: > > >This didn't work: > >13:04:14 Process exited with return code 1: /bin/sh /bin/sh -c db_alarm_prog 2>23 "Logical Log 333 Complete." "Logical Log 333 Complete." > >This worked: > >14:26:03 invoke_alarm(): /bin/sh -c 'db_alarm_prog 5 6 "Internal Subsystem>failure: 'MT'" "Attempting to bring listener thread down" ' -- David Williams Maintainer of the Informix FAQ Primary site (Beta Version) http://www.smooth1.demon.co.uk Official site http://www.iiug.org/techinfo/faq/faq_top.html I see you standin', Standin' on your own, It's such a lonely place for you, For you to be If you need a shoulder, Or if you need a friend, I'll be here standing, Until the bitter end... So don't chastise me Or think I, I mean you harm... All I ever wanted Was for you To know that I care