On Thu, Feb 11, 2010 at 07:36:23AM -0500, Leif Madsen wrote:
Jason Parker wrote:
Brian wrote:
Each time the server is rebooted Asterisk duly
deletes the manually created /var/run/asterisk directory - quite why it
does this I just don't know - perhaps it is a bug?
Your assumption is
On Fri, 2010-02-12 at 14:15 +0200, Tzafrir Cohen wrote:
{snip}
So the questions to ask are, I believe:
* Should asterisk here be run as root? If so: why?
It suits me to run it that way on the device concerned.
* Where should the astvarrundir be?
If you leave the defaults as they are (dictated
On Fri, Feb 12, 2010 at 12:28:53PM +, Brian wrote:
On Fri, 2010-02-12 at 14:15 +0200, Tzafrir Cohen wrote:
{snip}
So the questions to ask are, I believe:
* Should asterisk here be run as root? If so: why?
It suits me to run it that way on the device concerned.
Could you please be
On Fri, 2010-02-12 at 15:18 +0200, Tzafrir Cohen wrote:
On Fri, Feb 12, 2010 at 12:28:53PM +, Brian wrote:
On Fri, 2010-02-12 at 14:15 +0200, Tzafrir Cohen wrote:
{snip}
So the questions to ask are, I believe:
* Should asterisk here be run as root? If so: why?
It suits me to
Brian wrote:
If you leave the defaults as they are (dictated by (!) in asterisk.conf)
then the behaviour you get is Asterisk looking to /var/run/asterisk
which the OS deletes on reboot. The question is why is this the default
behaviour when it breaks systems that clear /var/run
Because it's
On Fri, 2010-02-12 at 10:20 -0600, Kevin P. Fleming wrote:
Brian wrote:
If you leave the defaults as they are (dictated by (!) in asterisk.conf)
then the behaviour you get is Asterisk looking to /var/run/asterisk
which the OS deletes on reboot. The question is why is this the default
On Fri, Feb 12, 2010 at 04:51:29PM +, Brian wrote:
On Fri, 2010-02-12 at 10:20 -0600, Kevin P. Fleming wrote:
Brian wrote:
If you leave the defaults as they are (dictated by (!) in asterisk.conf)
then the behaviour you get is Asterisk looking to /var/run/asterisk
which the OS
On Fri, 2010-02-12 at 19:20 +0200, Tzafrir Cohen wrote:
Adding documentation is what you do when things fail to work. I suspect
you use an older init.d script.
You are just being silly now. Good documentation is essential to
everything.
With regards to your comments about the init.d script,
On Fri, Feb 12, 2010 at 06:24:02PM +, Brian wrote:
On Fri, 2010-02-12 at 19:20 +0200, Tzafrir Cohen wrote:
Adding documentation is what you do when things fail to work. I suspect
you use an older init.d script.
You are just being silly now. Good documentation is essential to
Jason Parker wrote:
Brian wrote:
Each time the server is rebooted Asterisk duly
deletes the manually created /var/run/asterisk directory - quite why it
does this I just don't know - perhaps it is a bug?
Your assumption is incorrect. Some Linux distributions will empty /var/run/
on
Since upgrading from 1.6.1 to 1.6.2 I get this error on boot:
Unable to open pid file '/var/run/asterisk/asterisk.pid': No such file
or directory
Or if I try to connect to Asterisk:
Unable to connect to remote asterisk
(does /var/run/asterisk/asterisk.ctl exist?)
If I manually create
Brian,
It could be that the ownership/permissions on the directory are not correct.
Are you running asterisk as asterisk:asterisk or root:root?
Here is an article that lists the directories and what the
ownership/permissions on each one should be:
On Wed, 2010-02-10 at 08:54 -0500, Ken Leland III wrote:
Brian,
It could be that the ownership/permissions on the directory are not correct.
Are you running asterisk as asterisk:asterisk or root:root?
Here is an article that lists the directories and what the
ownership/permissions on
-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Brian
Sent: Wednesday, February 10, 2010 8:15 AM
To: Ken Leland III
Cc: asterisk-users@lists.digium.com
Subject: Re: [asterisk-users] Unable to open pid file
'/var/run/asterisk/asterisk.pid': No such file
On Wed, 2010-02-10 at 14:14 +, Brian wrote:
On Wed, 2010-02-10 at 08:54 -0500, Ken Leland III wrote:
Brian,
It could be that the ownership/permissions on the directory are not correct.
Are you running asterisk as asterisk:asterisk or root:root?
Here is an article that lists the
Brian wrote:
Each time the server is rebooted Asterisk duly
deletes the manually created /var/run/asterisk directory - quite why it
does this I just don't know - perhaps it is a bug?
Your assumption is incorrect. Some Linux distributions will empty /var/run/ on
boot, just as they do with
On Wed, 2010-02-10 at 11:24 -0600, Jason Parker wrote:
Brian wrote:
Each time the server is rebooted Asterisk duly
deletes the manually created /var/run/asterisk directory - quite why it
does this I just don't know - perhaps it is a bug?
Your assumption is incorrect. Some Linux
The other way on Debian/Ubuntu is just to test the existence of the dir and
create it if needed
If you add this to the /etc/init.d/asterisk near the start you should be fine
if ! [ -d /var/run/asterisk ] ; then
mkdir /var/run/asterisk
chown $AST_USER.$AST_GROUP /var/run/asterisk
On Thu, Feb 11, 2010 at 08:45:05AM +1300, Duncan Turnbull wrote:
The other way on Debian/Ubuntu is just to test the existence of the dir and
create it if needed
If you add this to the /etc/init.d/asterisk near the start you should be fine
if ! [ -d /var/run/asterisk ] ; then
19 matches
Mail list logo
