Thanks AT.
On 1/24/07, Axel Thimm <[EMAIL PROTECTED]> wrote:
On Tue, Jan 23, 2007 at 06:20:08PM +0100, Axel Thimm wrote:
> On Tue, Jan 23, 2007 at 03:54:49PM +0200, Tzafrir Cohen wrote:
> > On Tue, Jan 23, 2007 at 02:48:07PM +0100, Axel Thimm wrote:
> >
> > >
> > > If I call asterisk -r as root it succeeds, if as another user it will
> > > give Devraj's error message. That's probably how it is supposed to
> > > work, or not?
> >
> > Just a thought: shouldn't the asterisk user be allowed write access to
> > that control socket? Or maybe the asterisk group?
>
> The asterisk user is allowed, too, of course, the group not (yet).
>
> > (for quick&dirty shell scripts)
>
> I think that makes very much sense. The socket is created by asterisk,
> is there a parameter to specify permissions/umask of that socket?
Looks like all there is needed is to uncomment the following line in
the default config file:
[files]
astctlpermissions = 0660
But since upstream defaults to not do so and only have this done by
the user, I wouldn't like to change this policy on the package level.
--
Axel.Thimm at ATrpms.net
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
--
"I never look back darling, it distracts from the now", Edna Mode (The
Incredibles)
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
