On Thu, 2007-01-25 at 18:01 +0200, Tzafrir Cohen wrote:
> On Thu, Jan 25, 2007 at 01:37:50PM +0100, Tomislav ParĨina wrote:
> > In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] says...
> > > > Try safe_asterisk , for an easy way to start asterisk in background, 
> > > 
> > > a plain 'asterisk' is even better and safer.
> > > asterisk -U asterisk . is better. 
> > >   /etc/init.d/asterisk start
> > > is similar.
> > 
> > Why is this better than safe_asterisk?

the init.d init scripts bundled with asterisk are using safe_asterisk
and not calling the asterisk binary directly.

> E.g: because you have a valid PID file of the controlling process. If
> you actually want to kill it, you can.

Granted, its a good idea. the init.d scripts bundled with asterisk kill
safe_asterisk, which apparently works just as well (haven't looked at
safe_asterisk code, but its probably killing its child when it is being
killed, which should work well for any situation other then kill -9).

> And you don't need physical access to the system to get to the one and
> only real console. OTOH, if you do have physical access, you have full
> control of Asterisk, as you may inject custom dialplan.

I wasn't aware that running asterisk -r on a physical tty has any
advantages over running asterisk -r on a remote shell.

--
Oded Arbel
Atelis
[EMAIL PROTECTED]
Tel: +972-54-7340014
::..
In this world, truth can wait; she's used to it.


_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to