This is a discussion on Alarmprogram & Dynamic Server resource overflow:Locks within the Informix forums, part of the Database Server Software category; --> Hello All We have alarmprogram turned on but unfortunately, when the Server runs out of locks we recieve hundreds ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello All We have alarmprogram turned on but unfortunately, when the Server runs out of locks we recieve hundreds or even thousands of emails stating so - " Attention! : Dynamic Server resource overflow: 'Locks'." Is there a way to configure the alarm so that we get a limited number - say 10 or 50 emails rather than an email for each of the sessions and the locks that are overflowing? Thanks in Advance! Tom |
| |||
| tomcaml@yahoo.com wrote: > Hello All > > We have alarmprogram turned on but unfortunately, when the Server runs > out of locks we recieve hundreds or even thousands of emails stating > so - " Attention! : Dynamic Server resource overflow: 'Locks'." > > Is there a way to configure the alarm so that we get a limited number - > say 10 or 50 emails rather than an email for each of the sessions and > the locks that are overflowing? Take a look at my alarm program, eventalarm.c, in the package utils3_ak in the IIUG Software Repository. Basically it avoids this problem by making a record in a file of the last time it sent a message about a particular event id and only sends another email after N minutes have passed (N is configurable but defaults to 5 minutes) Art S. Kagel |
| ||||
| Gracias!!!! Art S. Kagel wrote: > tomcaml@yahoo.com wrote: > > Hello All > > > > We have alarmprogram turned on but unfortunately, when the Server runs > > out of locks we recieve hundreds or even thousands of emails stating > > so - " Attention! : Dynamic Server resource overflow: 'Locks'." > > > > Is there a way to configure the alarm so that we get a limited number - > > say 10 or 50 emails rather than an email for each of the sessions and > > the locks that are overflowing? > > Take a look at my alarm program, eventalarm.c, in the package utils3_ak in > the IIUG Software Repository. Basically it avoids this problem by making a > record in a file of the last time it sent a message about a particular event > id and only sends another email after N minutes have passed (N is > configurable but defaults to 5 minutes) > > Art S. Kagel |