[asterisk-bugs] [Asterisk 0016358]: [patch] new option: lockconfdir for protecting conf files in /etc/asterisk during reloads
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Mar 17 09:59:27 CDT 2010
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=16358
======================================================================
Reported By: raarts
Assigned To: jpeeler
======================================================================
Project: Asterisk
Issue ID: 16358
Category: Core/Configuration
Reproducibility: always
Severity: feature
Priority: normal
Status: closed
Target Version: 1.8
Asterisk Version: SVN
JIRA: SWP-533
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 2009-12-01 03:06 CST
Last Modified: 2010-03-17 09:59 CDT
======================================================================
Summary: [patch] new option: lockconfdir for protecting conf
files in /etc/asterisk during reloads
Description:
Hi,
because we regenerate asterisk config files externally, we need to protect
the /etc/asterisk directory with a lock. I'd like to put in a new config
option for asterisk.conf: lockconfdir. If yes, asterisk creates and
honoures the lock file during reloads. Defaults to 'no' of course.
Patch attached.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-03-17 09:59 lmadsen Status assigned => closed
2010-03-17 09:59 lmadsen Resolution reopened => fixed
======================================================================
More information about the asterisk-bugs
mailing list