Your assumption is correct.<div><br></div><div>however, </div><div><br></div><div>open file handles are not threadsafe and you cannot have 2 threads opening the same file and expect sane results. That's why syslog is a udp network server so it can serialize the log messages into a single threaded open file handle in the central syslog process.</div>
<div><br></div><div><br><div class="gmail_quote">On Tue, May 11, 2010 at 4:39 PM, paul bilke <span dir="ltr"><<a href="mailto:fsmail@conspiracy.net">fsmail@conspiracy.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I am working on a system that invokes a LUA script of the dial plan to handle interaction on the call.<br>
All is fine when running a single instance of the script (one call). The issue is when there is more than one call things become erratic.<br>
Right now the script opens a log file who's name is based on the date of the call and its DNIS using io.open with append.<br>
The script then writes lines to file as it runs detailing its actions. The same log function also uses posix.syslog to log the same information<br>
via syslog. All is fine when there is one call up.<br>
If there is more than one concurrent on two different DNIS's both log files a present but have output that was created by the other call.<br>
The syslog is sane but not the file of logging information. The time stamp will jump backward and pickup with information from the other call<br>
(can tell via the UUID)<br>
It is my assumption that each call should spin up a thread and they should share no data/variables/handles with other calls in the system. Looking at<br>
the logs indicates there is some issue but logging is not the only issue since it seems that call events updating state information is affecting the other<br>
call also.<br>
If my assumption on a isolated thread per call is incorrect let me know.<br>
I inherited this code and suspect that running an application out of the dialplan script is unconventional.<br>
Paul<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
Twitter: <a href="http://twitter.com/FreeSWITCH_wire">http://twitter.com/FreeSWITCH_wire</a><br><br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>
pstn:+19193869900<br>
</div>