[Asterisk-Users] Safely editing voicemail.conf

[BJ Weschke]

On 2/16/06, C F <shmaltz at gmail.com> wrote:
> I think you should discuss this with the bug marshals looks like a bug to me.
>
> On 2/16/06, John Goerzen <jgoerzen at complete.org> wrote:
> > We have a problem with Asterisk not locking voicemail.conf for update.
> >
> > It appears to not protect the file even against itself.  It certainly
> > doesn't use flock() to protect it against others.
> >
> > This is a problem for several reasons.  First, of course, people can be
> > hand-editing the file to add or remove users.  Secondly, automated
> > programs may be appending data to it for the same purpose.
> >
> > We've noticed corruption in our file that appears to occur when someone
> > is changing their passwords at the same time that the file is being
> > appended to.  From looking at app_voicemail.c, Asterisk does nothing
> > whatsoever to lock the file before modifying it.  That sounds bad to me.
> >
> > Has anyone else seen this problem?  What do you do to work around it?
> >
> > We're running Asterisk 1.2.1.
> >

 shmaltz is probably right as I haven't looked at the code yet to
verify this myself, but there's probably not a trivial way to lock it
from external entities editing it that is also cross-platform
compliant. :(

--
Bird's The Word Technologies, Inc.
http://www.btwtech.com/