From: Kristian K. <kri...@gm...> - 2007-05-03 16:27:18
|
On 5/3/07, Tony Plack <To...@pl...> wrote: > > I know I posted this before, but when you run Asterisk in verbose mode, > Asterisk does not release the console and fork a new thread. > > In AstLinux, this leaves the server "hung" just after the asterisk init > script and no other scripts run. Because it is hung, the inittab never runs > and you do not get the console prompt. > > Is it possible to add a "&" after the "asterisk -p" line in the > /etc/init.d/asterisk script? I don't think it will break things when > verbose mode is not used. > > It would also be nice to have a couple more tty entries in inittab for the > console. I am not sure the impact of this with non i586 devices, but it is > nice to have the extra consoles when tty1 gets hung on the inittab. > > Any thoughts? Tony, I run Asterisk in verbose mode all of the time. What changes did you make (command line arguments, config files, etc). I don't ever have the problems that you are describing. As far as extra ttys - screen is included by default. It is a much more flexible and memory efficient way to support multiple ttys. Are you familiar with it? -- Kristian Kielhofner |