Brett,<br>I believe you need the full path to the reply fifo.<br>Try:<br>echo -e ":address_dump:/tmp/my_fifo\n\n" > /tmp/opensips_fifo<br><br>you may also have a permissions ( chmod a+w /tmp/my_fifo ) and/or SELinux issue (very likely if SELinux is enabled, I posted a howto for SELinux in the list a number of months back)<br>
<br>Dave<br><br><div class="gmail_quote">On Mon, May 9, 2011 at 9:40 AM, Brett Nemeroff <span dir="ltr"><<a href="mailto:brett@nemeroff.com">brett@nemeroff.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello List,<div>So I've been doing some testing with the mi_fifo and found that it appears to be really fragile. Here's what I've done:</div><div><br></div><div>mkfifo /tmp/my_fifo</div><div>cat /tmp/my_fifo&</div>
<div>echo -e ":address_dump:my_fifo\n\n" > /tmp/opensips_fifo</div><div><div>*returns*</div><div>200 OK</div><div> 48 <1.2.3.4,2, 0, 0, NULL, NULL></div></div><div>** cat process ends</div><div>cat /tmp/my_fifo&</div>
<div><div>echo -e ":address_dump:my_fifo\n\n" > /tmp/opensips_fifo</div><div>** nothing</div><div><br></div><div>At this point, I can't make the fifo work again until I restart opensips. If I detach from the fifo (kill the cat, so to speak), and reattach it doesn't work. Nothing seems to make it responsive again. At first I though something was horribly broken, but then I removed one of my \n from the fifo command and now it works "as expected". Two new-lines shouldn't break the fifo, right?</div>
<div><br></div><div>Thanks!</div><div>-Brett</div><div><br></div><div><br></div><div><br></div><div></div></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>David Singer<br>