From: Kristian K. <kri...@gm...> - 2007-05-03 18:12:56
|
On 5/3/07, Tony Plack <To...@pl...> wrote: > > In the asterisk.conf file I have the following: > [options] > verbose = 20 ; Verbosity level for logging (-v) > highpriority = yes ; Execute with high priority (-p) > > If I remove the verbose, the asterisk will fork its process, with the > verbose, it does not fork. > > Just so you know, asterisk runs just fine, but the console is not available > and the mini-http never loads. > > Screen is great when dealing with a console, but the problem is that I > cannot log into the single default console because of the above issue, > therefore, screen is not available. > > Having the second console assures that if/when the main console gets blocked > (at least on the i586 platform), you have a separate login point. > Tony, Just as an FYI... I am VERY much against the idea of an "Asterisk console". It appears that option also enables the console, which is a bad idea. If you enable an "Asterisk console" security on the system becomes non-existant. Anyone can walk up to the box and have full access to Asterisk AND the shell (using !) as the user running Asterisk (usually root). Not good. Consoles are not platform specific but the ability for a virtual terminal is limited to systems with VGA video and a PS/2 mouse and keyboard. Many AstLinux systems only have a serial port. I have never had problems using multiple v's or "set verbose". If we solve this issue, screen will work quite well! -- Kristian Kielhofner |