I'm wondering if anyone is having problems when multiple users concurrently change their voicemail passwords.
Consider the following scenario (based on vm_change_password() in app_voicemail.c): - user1 wishes to change his password so voicemail.conf is opened and read into a buffer - user1 changes his password - user2 wishes to change his password so voicemail.conf is opened and read into a buffer - voicemail.conf is written with user1's modified password - voicemail.conf is rewritten with user2's modified password but not including user1's modified password because the voicemail.conf that was read by Asterisk when user2 wanted to change his password was read before the changed password of user1 got written back. It seems by looking at the code that this is how it is currently done. The file is not locked down once it is opened. So my question, is the above scenario correct or is there somewhere a lock which I missed out on? Jez ____________________________________________________________________________________ Want to start your own business? Learn how on Yahoo! Small Business. http://smallbusiness.yahoo.com/r-index _______________________________________________ --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