** Thanks everyone. I think I have enough material to make this work now.


On 1/13/06, L. J. Head wrote:

**
You could do something with perl to parse the ar.conf file and change the line from 0 to 1 for that particular log in question and then run an arsignal so that the server would know to re-read the config file...it's not quite API but it should work in theory




From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Alfred Differ
Sent: Thursday, January 12, 2006 4:24 PM
To: arslist@ARSLIST.ORG
Subject: Turning on logging from workflow


** Can it be done? That is the question.

I have a 6.3 system and an issue where the escalations drag to a stop. I'm not sure what is causing it, but I can see it stop if I happen to be running the escalation logging feature. I can't turn on logging and leave it on all day as it tends to write a lot of material. What I'd like to do is write an escalation pair that turns logging on and off occasionally at times just before I suspect something is going to cause problems.

I can write separate shell scripts to watch the log file and send the alarm when it grinds to a halt. That isn't a problem for me. What I need to know is if there is a special function call or something that will let me start escalation logging without having to do it manually or to stop/start my system.

Any help would be appreciated. I'm going to keep looking too.

--
-al This posting was submitted via the Web interface This posting was submitted via the Web interface




--
-al This posting was submitted via the Web interface