3 Feb
2005
3 Feb
'05
5:57 p.m.
/usr/local/ser/sbin/ser -P /var/run/ser.pid
and check the content of the pidfile (process-id)
But don't rely on the ser.pid. Sometimes it stays alive....
Tiny shellscript:
liveForever.sh
---------------------------------------------------------
#!/bin/bash
while [ 1 ]
do
if ! $(ps ax | grep -q '[s]er ')
then
...clean up....
...restart ser....
fi
sleep 5
done
---------------------------------------------------------
and put this line in your inittab:
ww:345:respawn:/path/to/your/liveForever.sh
Ricardo Martinez schrieb:
Hello list.
I have a question about reliability in SER. Suppose that for
certain reason, the process "ser" fails, and therefore the SIP Server is
down. Is there a way to keep trace of the "ser" process status?? and if the
process is not running start a script to restart the process. I know that
maybe the "crond" command could be useful for this purpose. Does someone
have any clue about this? Or maybe SER has his own "crond" module or
something.?
I really need and advice about this issue.
Thanks in advance
Regards,
Ricardo Martinez Ogalde.-
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers