**
With 6.3 the arsignal program contains a -e option for just the Escalations
 
Usage: arsignal -c hostname[:port] [sigArgument] - read configuration file
       arsignal -g hostname[:port] [sigArgument] - read group information and cache
       arsignal -l hostname[:port] [sigArgument] - read license information
       arsignal -a hostname[:port] [sigArgument] - update alert user information
       arsignal -u hostname[:port] [sigArgument] - read user information and cache
       arsignal -d hostname[:port] [sigArgument] - transfer signal to DSO process
       arsignal -p hostname[:port] [sigArgument] - transfer signal to application process
       arsignal -b hostname[:port] [sigArgument] - recache and reload archive definitions
       arsignal -e hostname[:port] [sigArgument] - recache and reload escalation definitions



From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
Sent: Wednesday, May 03, 2006 1:15 PM
To: [email protected]
Subject: Re: How to stop Arreror.log

**
 
Kathy,
 
Either restart your Remedy services or run the arsignal command with the -g option for it to re-read the def cache, which should tell the AR Server that the Escalation in question has been disabled.. Try that and check the outcome...
 
Joe

Kathy Morris <[EMAIL PROTECTED]> wrote:
**
I created an escalation -- which is not working.  I disabled the escalation, however in the arerror.log this is still running.  Why is the escalation still running, even though it is disabled?  The errors are filling up our disk space fast.  Is there a way to stop this from writing to the arreror.log?


Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates. __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___

Reply via email to