27 Jan
2005
27 Jan
'05
9:48 p.m.
You can use fork=no in ser.cfg and it will allow supervise to control
it, the only caveat is that SER can no longer be multihomed when it
doesn't fork. Also since SER only listens on the one interface you need
to make sure it's listening on the correct interface by passing the -l
flag in your run script in the /service directory.
-Evan
On Thu, 2005-01-27 at 18:49 +0100, Jan Janak wrote:
We have been using tool called monit:
http://www.tildeslash.com/monit/
Jan.
On 21-01 15:36, u2 wrote:
<http://cr.yp.to/djb.html>Hello,
did somebody success to control a SER proxy with D.J. Bernstein's
daemontools?
As soon as SER is run, it puts itself to the shell background. As far as
I found out, this behavior prevents the daemontools from controlling SER.
What did anybody already experiment with this toolkit? What do you use
to control you SER processes (auto-respawn, logging, etc.)?
It would be also great to use Bernstein's multilog to collect SER logs
in a comfortable manner (with per instance log, log rotation,
timestamps, etc).
What do you use here? Any recommendation?
Best regards,
Urs Uschmann
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers