Tzafrir Cohen wrote:
> On Thu, Apr 10, 2008 at 01:08:21PM -0400, Doug Lytle wrote:
>
>> Joshua Kinard wrote:
>>
>>> send "core set verbose 999" when connecting in.
>>>
>>>
>> I'm running Mandriva and found the line that had -vvv. I like mine at
>> 15, so just put 15 v's on that
On Thu, Apr 10, 2008 at 01:37:34PM -0400, Joshua Kinard wrote:
> -Original Message-
> Sent: Thursday, April 10, 2008 1:22 PM
>
> > 15? What do you need that for?
> >
> > IIRC the highest verbosity level is 5. anything more than that doesn't
> > change the clogging of your logs.
>
> Ah, 5
-Original Message-
Sent: Thursday, April 10, 2008 1:22 PM
> 15? What do you need that for?
>
> IIRC the highest verbosity level is 5. anything more than that doesn't
> change the clogging of your logs.
Ah, 5 is max? Kinda like gcc not supporting anything greater than -O3? Good
to know
-Original Message-
Sent: Thursday, April 10, 2008 1:08 PM
> Or maybe it's plain buggy. Bug reports are welcomed.
Nah, I think it was PEBKAC and PICNIC here :: sheepish grin ::
I tried adding --style options to the DAEMON var assignment, and it looks
like the -f check further down di
Tzafrir Cohen wrote:
> On Thu, Apr 10, 2008 at 01:08:21PM -0400, Doug Lytle wrote:
>
>> Joshua Kinard wrote:
>>
>>> send "core set verbose 999" when connecting in.
>>>
>>>
>> I'm running Mandriva and found the line that had -vvv. I like mine at
>> 15, so just put 15 v's on that
On Thu, Apr 10, 2008 at 01:08:21PM -0400, Doug Lytle wrote:
> Joshua Kinard wrote:
> > send "core set verbose 999" when connecting in.
> >
>
>
> I'm running Mandriva and found the line that had -vvv. I like mine at
> 15, so just put 15 v's on that line. Worked great.
15? What do you need t
On Thu, Apr 10, 2008 at 12:48:05PM -0400, Joshua Kinard wrote:
>
> Hmm, interesting, initially it wasn't working. Maybe I started it from
> outside of screen? Odd.
Or maybe it's plain buggy. Bug reports are welcomed.
>
> BTW, is it possible for the SuSE script to support a variable to pass
Joshua Kinard wrote:
> send "core set verbose 999" when connecting in.
>
I'm running Mandriva and found the line that had -vvv. I like mine at
15, so just put 15 v's on that line. Worked great.
Doug
--
Ben Franklin quote:
"Those who would give up Essential Liberty to purchase a littl
Hmm, interesting, initially it wasn't working. Maybe I started it from outside
of screen? Odd.
BTW, is it possible for the SuSE script to support a variable to pass args to
the daemon? Like perhaps modifying ASTARGS to be a changable param at the top
of the script? I like the verbose outpu
On Thu, Apr 10, 2008 at 11:43:18AM -0400, Joshua Kinard wrote:
>
> Seconded/thirded too. Went from 1.4.18 to 1.4.19, stopped using -c and went
> to background and connecting using -r, and colors disappeared for me as well.
> I'm using screen as well (ls -l --color=auto works fine in screen too
Joshua Kinard wrote:
> Seconded/thirded too. Went from 1.4.18 to 1.4.19, stopped using -c and went
> to background and connecting using -r, and colors disappeared for me as well.
> I'm using screen as well (ls -l --color=auto works fine in screen too).
>
The colors work if you use the suppl
Seconded/thirded too. Went from 1.4.18 to 1.4.19, stopped using -c and went to
background and connecting using -r, and colors disappeared for me as well. I'm
using screen as well (ls -l --color=auto works fine in screen too).
Is there a documented "fix" available, or is this more just an odd
Tzafrir Cohen wrote:
> On Wed, Apr 09, 2008 at 08:00:38PM -0400, Mike wrote:
>
>> Ah, not bad. When I start asterisk with "/usr/sbin/asterisk -c" I get the
>> colors, but if I start it without -c and then connect to the console using
>> "/usr/sbin/asterisk -r" I get no color.
>>
>> Since I wan
On Wed, Apr 09, 2008 at 04:23:38PM -0800, Mojo with Horan & Company, LLC wrote:
> Mike wrote:
> > Ah, not bad. When I start asterisk with "/usr/sbin/asterisk -c" I get the
> > colors, but if I start it without -c and then connect to the console using
> > "/usr/sbin/asterisk -r" I get no color.
>
On Wed, Apr 09, 2008 at 08:00:38PM -0400, Mike wrote:
> Ah, not bad. When I start asterisk with "/usr/sbin/asterisk -c" I get the
> colors, but if I start it without -c and then connect to the console using
> "/usr/sbin/asterisk -r" I get no color.
>
> Since I want this to be running in the back
ez
>> Sent: Wednesday, April 09, 2008 19:06
>> To: Asterisk Users Mailing List - Non-Commercial Discussion
>> Subject: Re: [asterisk-users] Jumped from 1.2.7 to 1.4.19,
>> missing CLI colors
>>
>> Correct me if I'm wrong, but if you run asterisk as a serv
e my cake and eat it too?
Mike
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Mik Cheez
> Sent: Wednesday, April 09, 2008 19:06
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [asterisk-users] Ju
Correct me if I'm wrong, but if you run asterisk as a service this
happens. There is/was some dispute as to the fallacy of using
'safe_asterisk' anyway.
Start it at the command line to see the pretty colors.
Mike wrote:
> Hi,
>
> I`ve just made a leap from * 1.2.7 to 1.4.19. It took a while
Hi,
I`ve just made a leap from * 1.2.7 to 1.4.19. It took a while to fix all
the deprecated stuff, but everything seems to be working fine now, except
for a little tiny thing. I lost all color in my CLI, which makes it harder
to debug. Is there something that needs doing? I didn't explicitely
19 matches
Mail list logo
