On Mon, Jul 04, 2005 at 05:51:25PM -0400, Jimmy Smith wrote:
> how about /etc/rc.local
>
> #a line that would work
> path/to/screen -d -m path/to/asterisk -vvgfc
>
The problem with adding stuff to rc.local is restarting. 'init 1; init
3' won't work as planned, for instance.
Also: people ten
That would work if for some reason ztcfg didn't refuse to run. I get the
proper output of ztcfg on the console but at runlevel it seems as if ztcfg
has never been run
On Mon, 4 Jul 2005, Jimmy Smith wrote:
how about /etc/rc.local
#a line that would work
path/to/screen -d -m path/to/asterisk
how about /etc/rc.local
#a line that would work
path/to/screen -d -m path/to/asterisk -vvgfc
-d -m Start screen in "detached" mode. This creates a new session but
doesn't attach to it. This is useful for system startup
scripts.
On 7/4/05, Carl
Did you check the log files looking for load errors?
Carlos Alperin
Senior System Engineer
Seneca Communications, LLC
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Remco Barende
Sent: Monday, July 04, 2005 3:06 PM
To: Asterisk Users
On Mon, Jul 04, 2005 at 09:55:46PM +0200, Roland Zagler wrote:
> i experienced that on some configs the "service asterisk restart" does
> not work correctly, so go to "/etc/rc.d/init.d" and edit the file
> "asterisk"
> and insert a "sleep 5" between stop and start in "restart".
Why is that?
'res
Hi,
after you have done "make", "make install" and maybe "make samples" in
asterisk source-dir just do a "make config" and all will be done for
you.
to check if it worked, simply issue "chkconfig --list asterisk" to see
the
runlevels asterisk is started or not.
to start zaptel drivers do the sam
