On 04/14/2010 09:22 AM, Darryl Chandler wrote: > Sounds good, although changing the init.d/asterisk file to include -vvv also > sets verbosity to 3. That file seems to be persistent across reboots.. is > that correct? (/etc/init.d/asterisk).
It's persistent across reboots, but it's your own personal init script now (meaning if you upgrade, your init script will overwrite any changes that we make). In general, you should not be modifying anything outside /mnt/kd If you want to get back to where you were, do the following: cd /oldroot/mnt/asturw/etc/init.d/ rm asterisk Then you should see the original script appear in /etc/init.d/ Darrick > Also - I was playing a bit, and trying to start asterisk as user/group > asterisk, and used chown on all the asterisk locations I could think of, > like /etc/asterisk; /var/lib/asterisk; /var/log/asterisk, etc. etc. I know > from documentation that editing these files directly is something we should > never do, and to stick with /mtn/kd/* for all edits. After a reboot, the > changes I made were all still there. What don't I understand about this > process? I thought all my changes would be gone once the system restarted > since I didn't make changes under /mnt/kd. > > As for the colour, I'm at a loss for why it doesn't work except if I put -c > in the startup - which is useless because asterisk is then stuck on the > terminal. > > -Darryl > > > > > -----Original Message----- > From: Darrick Hartman [mailto:dhart...@djhsolutions.com] > Sent: April 14, 2010 9:53 AM > To: astlinux-users@lists.sourceforge.net > Subject: Re: [Astlinux-users] Asterisk CLI Questions > > Guys, > > Take a look at the /stat/etc/rc.conf file. This has all of the possible > settings for your system. You should never edit this file, but you can > place variables from it into /mnt/kd/rc.conf (or > /mnt/kd/rc.conf.d/user.conf if using the web interface). > > ASTVERBOSE is the setting to set the asterisk verbosity. Set it to 3 > and you'll get most of what you need. > > If you read through the init script you'll see that mentioned in there too. > > I'm not sure about the color. > > Darrick > > On 04/14/2010 08:43 AM, Darryl Chandler wrote: >> OK. I was able to edit “/etc/init.d/asterisk” and add –vvvc to the >> startup options (it’s now asterisk -p -I –vvvgc) but now wherever I >> start the service, the CLI is not able to be quit without stopping the >> service. It seems that –c is required for the colour, but it implies –f >> which doesn’t allow you to quit the console. If I install centos on a >> machine, and yum install asterisk, this behavior is not the same. Colour >> works, and you get the normal prompt to login to the machine without >> being stuck in the asterisk CLI. Any ideas? >> >> -Darryl >> >> *From:* Chris Abnett [mailto:eldorado...@yahoo.com] >> *Sent:* April 13, 2010 8:58 PM >> *To:* 'AstLinux Users Mailing List' >> *Subject:* Re: [Astlinux-users] Asterisk CLI Questions >> >> I totally agree about the color.. I looked at the asterisk init script >> and color was not disabled.. in fact I was also missing syntax >> highlighting in nano and figured out that also.. Ill try some different >> things on my devel server and see if I can get color.. but I think it >> has to do with the terminal type that asterisk is running under… it may >> not be a color compatible terminal… >> >> -Christopher >> >> *From:* Darryl Chandler [mailto:dar...@sourcecable.ca] >> *Sent:* Tuesday, April 13, 2010 8:36 PM >> *To:* 'AstLinux Users Mailing List' >> *Subject:* Re: [Astlinux-users] Asterisk CLI Questions >> >> Ok, I’ll check the GUI for the verbosity level tomorrow. Looking at a >> production server we have, asterisk shows in “ps aux” as: >> “/usr/sbin/asterisk -U asterisk -G asterisk -vvvg –c” Do you know if it >> can be set to run the same way in astlinux? I’m sure you’d agree it’s >> easier to troubleshoot with the colour enabled, and having to stop/start >> asterisk isn’t realistic in a production environment. >> >> Thanks. >> >> -Darryl >> >> *From:* Chris Abnett [mailto:eldorado...@yahoo.com] >> *Sent:* April 13, 2010 4:24 PM >> *To:* 'AstLinux Users Mailing List' >> *Subject:* Re: [Astlinux-users] Asterisk CLI Questions >> >> I found the only way to enable the color on the console was to shut down >> asterisk and restart it with the –c console option.. >> >> I on lt do this on systems that I am working as developing and not on >> production because it will stop asterisk and restart it.. and of course >> once done you have to reboot and start it in background… >> >> Otherwise I also have no color… >> >> There is an option in the config file and I belive in lonnie’s GUI to >> set the verbosity level and it survives reboots… >> >> -Christopher >> >> *From:* Darryl Chandler [mailto:dar...@sourcecable.ca] >> *Sent:* Tuesday, April 13, 2010 3:43 PM >> *To:* 'AstLinux Users Mailing List' >> *Subject:* [Astlinux-users] Asterisk CLI Questions >> >> Hi guys, I have 2 questions to ask about the Asterisk CLI environment >> once astlinux starts up: >> >> Ø The colour isn’t showing up in the asterisk CLI on the console or ssh >> connections. Is this normal, or is there an option to enable it? >> >> Ø Is there a way to “core set verbose 3” by default? Our regular servers >> (non-ram disk/image) save this setting once set throughout reboots. >> Currently, every time the machine reboots, verbosity is back to 0. >> >> Thanks! >> >> -Darryl >> -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
