Hi John,
setting fork=no is not an option (you have only one UDP interface, no
TCP, no TLS)
I think it is an issue with upstart..there are many other apps that
fork at startup...
Regards,
Bogdan
John Khvatov wrote:
On Fri, Apr 03, 2009 at 08:26:09PM +0200, Iñaki Baz Castillo wrote:
On Mon, Apr 06, 2009 at 07:31:57PM +0300, Bogdan-Andrei Iancu wrote:
Hi John,
setting fork=no is not an option (you have only one UDP interface, no
TCP, no TLS)
I think it is an issue with upstart..there are many other apps that
fork at startup...
And this fork is just
Hi John,
i'm using monit (see http://mmonit.com/monit/ ) for a long time - quite
nice;
Also you may consider nagios http://www.nagios.org/
Regards,
Bogdan
John Khvatov wrote:
On Mon, Apr 06, 2009 at 07:31:57PM +0300, Bogdan-Andrei Iancu wrote:
Hi John,
setting fork=no is not an
Hi Bogdan,
On Mon, Apr 06, 2009 at 10:02:49PM +0300, Bogdan-Andrei Iancu wrote:
Hi John,
i'm using monit (see http://mmonit.com/monit/ ) for a long time - quite
nice;
Also you may consider nagios http://www.nagios.org/
Regards,
Bogdan
Thanks.
--
John Khvatov
El Viernes 03 Abril 2009, John Khvatov escribió:
Hello!
Can I run opensips in the foreground in daemon mode - multiple processes
for each network interface?
I need it to manage the opensips service by upstart [1].
[1] http://upstart.ubuntu.com/
If you set log_stderror=no then OpenSIPS
On Fri, Apr 03, 2009 at 08:26:09PM +0200, Iñaki Baz Castillo wrote:
If you set log_stderror=no then OpenSIPS output will be logged in the
terminal. But you can close safely this terminal session and OpenSIPS will
remain working.
BTW, which requeriments has upstart?
Upstart until release
On Fri, Apr 03, 2009 at 11:27:31PM +0400, John Khvatov wrote:
On Fri, Apr 03, 2009 at 08:26:09PM +0200, Iñaki Baz Castillo wrote:
If you set log_stderror=no then OpenSIPS output will be logged in the
terminal. But you can close safely this terminal session and OpenSIPS will
remain
