sms server component: anyone using it ?

This is a multipart message in MIME format.
--===============0225242171==
Content-Type: multipart/alternative;
	boundary="=_alternative 0032FA14C125703E_="

This is a multipart message in MIME format.
--=_alternative 0032FA14C125703E_=
Content-Type: text/plain; charset="US-ASCII"

Hi,

I'm using smsclient together with nagios.

sometimes, when a lot of alerts need to be sent out, a lot fo smsclient 
processes are waiting for the active process to be finished, and as a 
result, we have had cases where the events are actually sent out in the 
wrong order (first, you get the 'everything ok' message, and afterwards 
you get the 'critical problem' alert for the same incident).

To avoid this, i was looking for a way to queue the message so that 
smsclient would process them as FIFO (first in first out).

I noticed that the source contained a server and a queue subdirectory, but 
it's hardly documented, and it doesn't get built automatically.

Is someone using smsclient in this way, and how does it actually work (is 
it stable ?).
or perhaps some people have other suggestions to my problem ?


regards,

Tom.


---------------------------------------------------------------------------
Tom Van Overbeke - ABSI Unix System Engineer
email: [email protected]
Tel: +32 2 333 40 00 - Fax: +32 2 332 34 69
website: http://www.absi.be
---------------------------------------------------------------------------

--=_alternative 0032FA14C125703E_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">I'm using smsclient together with nagios.</font>
<br>
<br><font size=2 face="sans-serif">sometimes, when a lot of alerts need
to be sent out, a lot fo smsclient processes are waiting for the active
process to be finished, and as a result, we have had cases where the events
are actually sent out in the wrong order (first, you get the 'everything
ok' message, and afterwards you get the 'critical problem' alert for the
same incident).</font>
<br>
<br><font size=2 face="sans-serif">To avoid this, i was looking for a way
to queue the message so that smsclient would process them as FIFO (first
in first out).</font>
<br>
<br><font size=2 face="sans-serif">I noticed that the source contained
a server and a queue subdirectory, but it's hardly documented, and it doesn't
get built automatically.</font>
<br>
<br><font size=2 face="sans-serif">Is someone using smsclient in this way,
and how does it actually work (is it stable ?).</font>
<br><font size=2 face="sans-serif">or perhaps some people have other suggestions
to my problem ?</font>
<br>
<br>
<br><font size=2 face="sans-serif">regards,</font>
<br>
<br><font size=2 face="sans-serif">Tom.</font>
<br>
<br>
<br><font size=2 face="sans-serif">---------------------------------------------------------------------------<br>
Tom Van Overbeke - ABSI Unix System Engineer<br>
email: [email protected]<br>
Tel: +32 2 333 40 00 - Fax: +32 2 332 34 69<br>
website: http://www.absi.be<br>
---------------------------------------------------------------------------<br>
</font>
--=_alternative 0032FA14C125703E_=--


--===============0225242171==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--

-----------------------------------------------------------------------