#execing the same file multiple times led to warning messages saying that the same...
authorMark Michelson <mmichelson@digium.com>
Mon, 5 May 2008 22:14:06 +0000 (22:14 +0000)
committerMark Michelson <mmichelson@digium.com>
Mon, 5 May 2008 22:14:06 +0000 (22:14 +0000)
commit276118a776b1ecbb137fbb9a9e8463b3bae244f9
tree5f84546cf3275f8c6822b126bf378a83b7e19cca
parentfc120bf827ca3a38cd429c53051f6e0b5322099c
#execing the same file multiple times led to warning messages saying that the same file was
being #included twice. This was due to the fact that #exec created a temporary file which
was then #included. The name of the temporary file was the name of the #exec'd file, with
the Unix timestamp and thread ID concatenated. The issue was that if multiple #exec statements
of the same file were reached in the same second, then the result was that the temporary files
would have duplicate names. To resolve this, the temporary file now has microsecond resolution
for the timestamp portion.

(closes issue #12574)
Reported by: jmls
Patches:
      12574.patch uploaded by putnopvut (license 60)
Tested by: jmls, putnopvut

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@115329 65c4cc65-6c06-0410-ace0-fbb531ad65f3
main/config.c